Twitter | Search | |
Andrew Nacin
Erstwhile , , Lead Developer. Tweets are my own. Vote.
35,132
Tweets
1,756
Following
28,530
Followers
Tweets
Andrew Nacin Oct 19
Replying to @helenhousandi
I guess, and I'm sure you're already there, I'd personally want to make the paths more testable (sorry 😓) and then build both tools and automated tests around them, rather than a primary emphasis on docs.
Reply Retweet Like
Andrew Nacin Oct 19
Replying to @helenhousandi
trunk/tools? not the best, not the worst.
Reply Retweet Like
Andrew Nacin retweeted
Emily Oct 12
“i stay out of politics” is such a weird way to spell “my rights as a human being aren’t up in the air every 4 years and i have no problem with the fact that yours are”
Reply Retweet Like
Andrew Nacin Oct 2
Replying to @evansolomon @Krogsgard
I’d be recommending The Newsroom.
Reply Retweet Like
Andrew Nacin Sep 25
Replying to @tollmanz @desrosj and 6 others
Sept 30 was originally going to be game 6, then Tampa won in 6 letting them move everything up. My guess there was a desire or need to have games on certain nights and it just worked out this way.
Reply Retweet Like
Andrew Nacin Sep 25
Removing Jim Orbin from this thread (again)
Reply Retweet Like
Andrew Nacin Sep 19
Replying to @anthonydpaul
A *lawyer* didn't listen to a UX designer or researcher.
Reply Retweet Like
Andrew Nacin Sep 17
Replying to @ToughCallBlog
Those should be! But this definitely isn’t.
Reply Retweet Like
Andrew Nacin Sep 15
Replying to @desrosj @tollmanz and 7 others
Longstanding policy has been that picks can be changed up until puck drop. There have been strategic changes in the past. That said we’ve never seen the gamesmanship of two people constantly switching picks like
Reply Retweet Like
Andrew Nacin Sep 13
Replying to @elisewho
Reply Retweet Like
Andrew Nacin Aug 29
There's also a huge difference in the distance off the boards. The Ritchie hit was 6 feet off the boards, in no man's land, far more violent, puck gone, no chance of ever being a clean hit. Even without injury to Gourde, these can't be penalized the same.
Reply Retweet Like
Andrew Nacin Aug 29
Replying to @ToughCallBlog
I'm not saying the first shouldn't have been a penalty, but distance traveled aside, the original comparison shows the puck is there and the hit took place much closer to the boards. Huge difference here.
Reply Retweet Like
Andrew Nacin Aug 21
Have we totalled the scores yet? Probably QR and first round separately.
Reply Retweet Like
Andrew Nacin Aug 21
Replying to @XedinUnknown @Rarst
25% of sites running the version of WordPress released a week ago run PHP < 7.1.
Reply Retweet Like
Andrew Nacin Aug 21
Replying to @XedinUnknown @Rarst
1) the proposal is to move to 7.1, so add another 10%, 2) 25% of sites is still tens of millions of users, many who don't know what PHP is, 3) our previous targets to jump to 5.2 (from 4) and 5.6 (from 5.2) were under 5-10% usage across the board
Reply Retweet Like
Andrew Nacin Aug 20
Replying to @michaeldance @Rarst
Probably not many! 5.5 was released a week ago. That's the benefit of the version crosstabs.
Reply Retweet Like
Andrew Nacin Aug 19
Replying to @Rarst
I'm not sure why it hasn't been a priority, but I & others have pulled it for others before and have posted it publicly as well. I can do the same after my vacation (I should put Twitter down). Last I checked: 25% of sites running WP 5.5 were < PHP 7.1. Way too early to do this.
Reply Retweet Like
Andrew Nacin Aug 19
Replying to @Rarst
This is _obviously_ a key philosophical decision that should be made by the project lead. And for what it's worth, our philosophies and standards on this have been consistent for more than a decade. The numbers strongly suggest it’s too early to drop PHP 5.6.
Reply Retweet Like
Andrew Nacin Aug 15
Replying to @whyisjake @trepmal
This is a lot more than a single change to WP_Query. Quietly making `0 == ""` be false is 😬😬😬
Reply Retweet Like
Andrew Nacin Aug 15
Replying to @trepmal
Lol it passed 44–1 😬
Reply Retweet Like