←back to thread

581 points antr | 2 comments | | HN request time: 0.42s | source
Show context
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 #
1. 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 #
2. 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.