I just talked with a driver. He said the 80% is correct, gross. Because everyone is a contractor the government takes another 30% on top of it. Plus they have to pay their own insurance, repair, gas, etc. so after everything is said and done, he makes about $13/hr. (This is inside San Francisco.)
I think it's because the article clearly names the two researchers, while WIRED is a faceless organization. It's a lot easier to get mad and blame the one with a face.
Same experience here. Back when I used Telerik they where some of the largest and slowest components I'd ever seen. Even their own homepage was unbearably slow at the time. This was many many years ago.
"It's old and crummy, easily one of the worst designed popular sites on the internet."
I love Reddit's design, it's very effective and to the point. You don't visit Reddit to view Reddit, you visit to read posts and comments. The design gets out of the way and lets you do that.
The magic button to wake up for me was having a schedule. I goto bed and wake up at the same time every day (even the weekends). It took me months, but forcing myself to physically get out of bed every morning did the trick. Now I wake up without an alarm clock.
War is also a great reason to horde. The History of the Peloponnesian War talks about people burying their money in hopes the the conquering army won't find it. Then you can go back and retrieve it later.
I have a friend who's small business was killed by Paypal. He had a board game shop (about five employees), but most of his business was online. He used Paypal as his bank account (dumb idea, I know.) During a christmas rush Paypal suddenly froze the account. I don't remember the exact reasons they gave, but it was something like he had too much money or was receiving money too fast.
> Perhaps 70% of developer time is spent dealing with parsing, serialization, and persistence. Values are encoded to and from JSON, to and from various binary formats, and to and from various persistent data stores… over and over again.
This is not my experience at all. I've spent maybe an hour or two in the last few months on parsing, serialization, and persistence. For the work I do, these are all solved problems.
> Another 25% is spent on explicit networking. We don’t merely specify that a value must be sent from one node to another, we also specify how in exhaustive detail.
Honestly I'm not sure what the author means by this. If I have a value others might want to know about, I just trigger an event. There is no "exhaustive detail' going on. (Plus events are easy to grep).
>Somewhere in between all this plumbing code is a tiny amount of interesting, pure computation, which takes up the remaining 5% of developer time. And there’s very little reuse of that 5% across applications, because every app is wrapped in a different 95% of cruft and the useful logic is often difficult to separate!
Boiler plate code used to be an issue, but the languages I still use have ways around it. (macros, first class functions, extending, etc). We build modules and libraries and controls, all reusable code that lets me spend most of my time being bored in meetings.
It makes sense, that's roughly the length of a movie. http://www.cinemablend.com/television/Unsurprising-Netflix-S...