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
- Most Technical Problems Are Really People Problemsblog.joeschrag.com
- How I Find Problems to Solve as a Staff Engineerlalitm.com
- Mistakes engineers make in large established codebasesseangoedecke.com
- Don't Call Yourself A Programmer, And Other Career Advice | Kalzumeus Softwarekalzumeus.com
- Reflections on 10,000 Hours of Programming | Matt Rickardmatt-rickard.com
- AddyOsmani.com - The Next Two Years of Software Engineeringaddyosmani.com
- Essays on programming I think about a lot | benkuhn.netbenkuhn.net
- How to waste your career, one comfortable year at a timeapoorvagovind.substack.com
- How I ship projects at big tech companiesseangoedecke.com
- How To Do Lessalexturek.com
- Advice to Myself When Starting Out as a Software Developer - The Pragmatic Engineerblog.pragmaticengineer.com