←back to thread

581 points antr | 1 comments | | HN request time: 0.337s | source
Show context
g20 ◴[] No.6223701[source]
20% time isn't dead -- I have been using it at Google consistently for over 7 years, and it has immensely benefited me. You don't need any permission, at least in engineering.

However, I would agree that it is "as good as dead". What killed 20% time? Stack ranking.

Google's perf management is basically an elaborate game where using 20% time is a losing move. In my time there, this has become markedly more the case. I have done many engineering/coding 20% projects and other non-engineering projects, with probably 20-40% producing "real" results (which over 7 years I think has been more than worth it for the company). But these projects are generally not rewarded. Part of the problem is that you actually need 40% time now at Google -- 20% to do stuff, then 20% to tell everyone what you did (sell it).

I am a bit disappointed that relatively few of my peers will consciously make the tradeoff of accepting a slower promotion rate in return for learning new things. Promotion optimizes for depth and not breadth. Breadth -- connecting disparate ideas -- is almost invariably what's needed for groundbreaking innovation.

replies(5): >>6223952 #>>6223999 #>>6224002 #>>6224655 #>>6227838 #
◴[] No.6223952[source]
ksk ◴[] No.6224162[source]
>I don't understand why engineers who don't want to be managers give a shit about corporate promotions or corporate ladders.

HR/MBA types value titles, buzzwords and other nonsense because most of them are incapable of actually parsing a technical resume. So, if you're going to look for a job, filling in your title as "developer" over a period of multiple years is a losing strategy.

By the same accord, without titles, buzzwords, etc as an engineer I won't be able to differentiate between resumes of a regular graduate level physics educator and one who is capable of nobel prize level research.

replies(1): >>6226883 #
1. VladRussian2 ◴[] No.6226883[source]
>By the same accord, without titles, buzzwords, etc as an engineer I won't be able to differentiate between resumes of a regular graduate level physics educator and one who is capable of nobel prize level research.

if you're in the position to make a hiring decision and can't make such differentiation - well, yep, that is what we have in software engineering. In physics the situation seems to be a bit (though not much) better, in part because of CVs, in part because the network is smaller.