[addy_osmani]

Hey folks. Author of this post here. I sincerely apologize, this was accidentally published live prematurely (my fault). It’s got a number of style and structure issues I’ve been working through locally (you are spot on regarding the heading feedback). I have taken it down and will be publishing it in the future once it is actually complete.

[trevcanhuman]

Honestly, I thought that was the joke (see the twitter algorithm[0]). That there actually aren't much insights from Google regular software engineers could relate to. As other comments have said, Google is the company who can afford to fuck up the most.

[0] https://news.ycombinator.com/item?id=31160546

[jdhendrickson]

Thanks for posting this reply to the article, I thought you had taken it down because half the people commenting seem to have forgotten a real human being exists behind the blog post.

Looking forward to reading it when you publish the revised version, though I'm unsure how I would know. (I guess I should check and see if you have RSS)

I wish the civility rules were enforced here a bit more stringently sometimes.

[amardeep]

Hi Addy,

It is sad to see that more often than not, the top comments on any article are overly negative or even vitriolic and any interesting discussion languishes deeper in the article.

I read your draft, and it is full of excellent advice. Some of it being which I also find very important, some which gives me food for thought and some which I am happy to be reminded of again. I look forward to your finished post.

[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.

[julianbuse]

Hopefully it doesn't get cancelled a week before it's finally ready.

[hamstrung]

I look forward to your post (perhaps after another 10 years) about testing before release and your use of CD.