Hacker News new | past | comments | ask | show | jobs | submit login

Not sure about the policy, but a few years back I heard from Qi Lu (who now runs Applications and Services) that even though he manages far more than that, he still attempts to read code regularly, even if his schedule doesn't permit him to write code himself. I'm sure his senior engineers are more than happy to ask down the hierarchy "send the code you're most proud of, or something that represents a critical piece of infrastructure or bottleneck to understand, and it'll be read all the way up the chain." In fact, now that I think about it, the morale side effects probably make this a great practice!

On a separate note, that tidbit has stuck with me years later - I heard it as an intern, and I think it's one of the things that really solidified in my mind that I could stick to my technical roots even if I went all the way down the path of engineering leadership. As I find myself writing more and more specs these days, I'm glad to be reminded of it.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact