Hacker Newsnew | comments | show | ask | jobs | submit | xiongchiamiov's comments login

We ran some analyses and determined the rise is not due to an increase in spambots. I don't know the specifics of how that was determined, sorry.

-----


R is awful. It's full of decisions made by people who seem to not have much programming experience, in that they seem good at the time but cause major issues later on. See, for instance, http://www.talyarkoni.org/blog/2012/06/08/r-the-master-troll... , http://blog.revolutionanalytics.com/2008/12/use-equals-or-ar... , http://shape-of-code.coding-guidelines.com/2012/02/29/parsin... , and the necessity of http://tim-smith.us/arrgh/ (I wrote up some stuff about the *apply functions, but not yet in a form suitable for the guide: https://github.com/tdsmith/aRrgh/issues/18 ) .

-----


They're just like other default subreddits, which is to say that you can unsubscribe from them. I only resubscribed recently because I started working at reddit and figured I should know what's going on in my own company.

-----


http://www.nngroup.com/articles/participation-inequality/ if you're looking for an article on it.

-----


> That said, it looks like a nice site, a crowdsourced iFixIt.

We're already crowd-sourced! http://www.ifixit.com/Contribute Only about half our guides are staff-created.

> (I'd me more willing to contribute if the TOS wasn't so restrictive, but since I still own my content I don't mind so much"

Good news! Everything on iFixit is CC BY-NC-SA: http://www.ifixit.com/Info/Licensing (but you still own your content).

-----


So what I don't get is why the function names needed to be of a certain length, since he's hard-coding the buckets.

-----


When do you do code review?

-----


We use a review script that creates a temporary branch in github and sends an email to everyone you specify to review it. We then kill that branch when the review is over. Any time you push code, you run our test suite on your changes then create a review. Since these are encouraged to be small and behind config flags to not affect all our users immediately, it happens quite often. Once feedback is taken from the review you enter our push queue yourself and push it out yourself. If the code is possibly dangerous, we recommend those pushes wait from Friday night to Monday morning for safety's sake.

-----


> Realistically, how many people repair Android or non-Apple phones? How many iPhone users would, when faced with a broken phone, try to fix it themselves rather than take it to the Apple store for repairs?

Not enough, and that's the problem. iFixit's purpose for existing is to get people repairing their things (electronic or otherwise); this is why we make guides and sell tools and parts, why we make all our guides freely available under a Creative Commons license, and why we spend a lot of time and effort convincing people that yes, they can repair things.

So when a corporation makes a visible effort to discourage these same people, we get frustrated. Yes, most Apple consumers don't want to repair their iDevices. But they never will if Apple continues discouraging them.

-----


The article is from Jan 20 2011; since then we've designed our own.

-----


It's a call that was being made (only) when the page loaded.

-----

More

Guidelines | FAQ | Support | API | Lists | Bookmarklet | DMCA | Y Combinator | Apply | Contact

Search: