3 ms·
It's most likely from Google's dev time program where a dev gets to work on a pet project 20%(?) of their time. That's why a ton of new projects come out of goo
by xeromal 5y ago
It's most likely from Google's dev time program where a dev gets to work on a pet project 20%(?) of their time. That's why a ton of new projects come out of google but get canned in a few years.
- harry8 5y agoDoes that still exist as a policy?
- hn_go_brrrrr 5y agoThe policy still exists. The practice is dying out, however.
- harry8 5y agoI don't understand. People would rather spend a day per week working on google's stuff than their own project?
- thesimon 5y agoWorking on your own projects won't get you promoted I would guess.
- mkr-hn 5y agoUnless that project is a messaging app.
- iamevn 5y agoProjects aren't typically scheduled to account for it in my experience. If I took that much time to work on something that's not an OKR then I'd just be falling behind.
- harry8 5y agoSo you totally can work on your own project for 20% of your time but you won't get 20% of your time to work on your project. Right. So the policy is dead with only a dishonest echo remaining..? Doesn't even qualify as evil anymore on google's standards, but when google hired freelance recruiters were ringing me several times a week it really would have. Those were the days, we used to think microsoft were horrible. And they were!