AddyOsmani.com - 21 Lessons From 14 Years at Google
addyosmani.com · 2,269 words · saved by 4 readers
Lessons learned from 14 years of engineering at Google, focusing on what truly matters beyond just writing great code.
When I joined Google ~14 years ago, I thought the job was about writing great code. I was partly right. But the longer I’ve stayed, the more I’ve realized that the engineers who thrive aren’t necessarily the best programmers - they’re the ones who’ve figured out how to navigate everything around the code: the people, the politics, the alignment, the ambiguity. These lessons are what I wish I’d known earlier. Some would have saved me months of frustration. Others took years to fully understand. None of them are about specific technologies - those change too fast to matter. They’re about the pat
saved by
related reading
- Drunk Post: Things I’ve Learned as a Senior Engineerluminousmen.substack.com
- What Actually Makes You Seniorterriblesoftware.org
- Mistakes engineers make in large established codebasesseangoedecke.com
- How I Find Problems to Solve as a Staff Engineerlalitm.com
- The maze is in the mouse. What ails Google. And how it can turn… | by Praveen Seshadri | Mediummedium.com
- AI is removing the middle class of software engineeringblog.florianherrengt.com
- The Friendship That Made Google Huge | The New Yorkernewyorker.com
- Good engineers are right, a lotseangoedecke.com
- https://danluu.comdanluu.com
- Good Engineer/Bad Engineerterriblesoftware.org
- What I learned getting acquired by Googleshreyans.org
- Why I Ignore The Spotlight as a Staff Engineer - Lalit Magantilalitm.com