←back to thread

581 points antr | 7 comments | | HN request time: 0.437s | source | bottom
1. smackfu ◴[] No.6223589[source]
Honestly, this completely makes sense given how Google has been killing off non-profitable products lately. Why pay engineers to work on projects that will never meet a business case? This isn't the olden days of Google, where they would shovel anything out there and see if it stuck.
replies(4): >>6223739 #>>6223773 #>>6223980 #>>6224660 #
2. zmb_ ◴[] No.6223739[source]
The same reason why a VC fund will invest in 10 startups knowing that 9 will have to be closed down as failures. 20% time meant that Google was continually making those bets in various areas, knowing that most will fail but that a few will succeed in a big way.

They now seem to think that their management has obtained good enough crystal balls to be able to determine beforehand which of the potential products will succeed and which will fail. Meaning that they can scrap the 20% time and put all their "wood behind the few arrows" they have determined will succeed (you know, like Google+).

replies(1): >>6238294 #
3. betterunix ◴[] No.6223773[source]
"Why pay engineers to work on projects that will never meet a business case?"

You need your engineers to put up with mundane, boring work. Paying them to spend a minority of their time on an interesting project helps.

replies(1): >>6224661 #
4. Laremere ◴[] No.6223980[source]
Google Wave failed quite horribly. However the resulting technology developed has been rolled into Docs, revolutionizing how Docs is used for collaboration.

There was a good image I saw on reddit awhile back that I can't find off hand. On the left was titled what most people view success and failure as, and it had a single branch, you fail or you succeed. Then it had what successful people view it as, and it was a chain of failure after failure finally leading to a success.

If you eliminate failure, you eliminate the success you gain from learning from failures.

5. mindcrime ◴[] No.6224660[source]
Why pay engineers to work on projects that will never meet a business case?

Isn't that begging the question in regards to whether or not you can know, ahead of time, which projects will or won't become viable and have a supporting business case?

6. cpncrunch ◴[] No.6224661[source]
The 20% thing isn't really much of a perk anyway. I would only ever work for a company that let me work whenever I wanted, take naps whenever I wanted, go for walks whenever I wanted, and work on other projects. I do this at my current job, and I still end up being more productive in my actual work than any other developer I've ever met (and more productive than the average google engineer, I'd venture to say). I run the company, so I guess I can decide how I work :)

See also the "people simply empty out" article posted on HN. Google seems to be falling for the PHB fallacy that people are just machines that crank out code. Perhaps that is what google is becoming, but I certainly wouldn't want to work there.

7. smackfu ◴[] No.6238294[source]
It really depends on the real stats though. Because if only 1 out of 100 20% projects is worth anything, maybe it's just not a good use of your engineers. Like a VC fund with too low a success rate just goes out of business.