✳flâneur — a map of the web's best reading
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
Explore this link on the map →saved by
related reading
- Drunk Post: Things I’ve Learned as a Senior Engineerluminousmen.substack.com
- Mistakes engineers make in large established codebasesseangoedecke.com
- The maze is in the mouse. What ails Google. And how it can turn… | by Praveen Seshadri | Mediummedium.com
- The Friendship That Made Google Huge | The New Yorkernewyorker.com
- Good engineers are right, a lotseangoedecke.com
- https://danluu.comdanluu.com
- claude code is not making your product betterethanding.substack.com
- rotorlab.tamu.edu/me489/README/2010 ASME Unwritten_Laws_of_Enginering.pdfrotorlab.tamu.edu
- Choose Boring Technologyboringtechnology.club
- What I learned getting acquired by Googleshreyans.org
- Software Engineering - The Soft Parts | Peng Jie's Blogjiepeng.me
- Things they didn't teach you about Software Engineeringvadimkravcenko.com