←back to thread

581 points antr | 1 comments | | HN request time: 0.213s | source
Show context
dekhn ◴[] No.6224161[source]
I am a Googler. I will only speak to my personal experience, and the experience of people around me: 20% time still exists, and is encouraged as a mechanism to explore exciting new ideas without the complexity and cost of a real product.

My last three years were spent turning my 20% project into a product, and my job now is spent turning another 20% project into a product. There was never any management pressure from any of my managers to not work on 20% projects; my performance reviews were consistent with a productive Googler.

Calling 20% time 120% time is fair. Realistically it's hard to do your day job productively and also build a new project from scratch. You have to be willing to put in hours outside of your normal job to be successful.

What 20% time really means is that you- as a Google eng- have access to, and can use, Google's compute infrastructure to experiment and build new systems. The infrastructure, and the associated software tools, can be leveraged in 20% time to make an eng far more productive than they normally would be. Certainly I, and many other Googlers, are simply super-motivated and willing to use our free time to work on projects that use our infrstructure because we're intrinsically interested in using these things to make new products.

replies(7): >>6224194 #>>6224827 #>>6225858 #>>6226177 #>>6227445 #>>6230638 #>>6241822 #
1. aryastark ◴[] No.6226177[source]
> Calling 20% time 120% time is fair

Every place I've worked has allowed employees to come in and work weekends on projects that would help the company. I guess those places just weren't innovative (read: arrogant) enough to rebrand it as an employee benefit.