[troelsSteegin]

I look forward to reading the completed post, I think there is a lot of good stuff in the draft.

What I noticed from the draft: There's nothing obvious about Google per se, in terms of the material. It could be company X you've been working at. Also, insights cumulatively cover junior dev, senior dev, and some manager experiences. So, audience for this particular piece was not clear to me.

I am surmising this piece complements your "Efficient Engineering" work-in-progress. I'll be curious to read that too.

[jka]

I'm guessing here, but I think the author's intent was to share knowledge that's generally applicable in other software engineering environments, rather than learnings that might be specific to Google (those could be both curiosity-building and/or also frustrating for other people to read, if they don't have access to the same systems).

Similarly, it'd likely be possible to learn many of the same findings at other companies -- Google (and the author) have been fortunate to encounter lots of tricky scaling and human issues in technology, and to evaluate potential strategies to deal with those, and it's good to see that knowledge shared.