✳flâneur — a map of the web's best reading
Why I Ignore The Spotlight as a Staff Engineer - Lalit Maganti
lalitm.com · 2,281 words · saved by 1 readers
An alternate path for Staff+ engineers that optimizes for systems over spotlights and stewardship over fungibility.
Discussed on Hacker News , lobste.rs and r/programming. Lately I’ve been reading Sean Goedecke’s essays on being a Staff+ engineer. His work (particularly Software engineering under the spotlight and It's Not Your Codebase ) is razor-sharp and feels painfully familiar to anyone in Big Tech. On paper, I fit the mold he describes: I'm a Senior Staff engineer at Google. Yet, reading his work left me with a lingering sense of unease. At first, I dismissed this as cynicism. After reflecting, however, I realized the problem wasn’t Sean’s writing but my reading. Sean isn't being bleak; he is accurate
Explore this link on the map →saved by
related reading
- Don't End The Week With Nothingtraining.kalzumeus.com
- AddyOsmani.com - 21 Lessons From 14 Years at Googleaddyosmani.com
- Choose Boring Technologyboringtechnology.club
- Stop just using “Frontend” or “Backend” to describe the Engineering you like - Michelle Limmichellelim.dev
- Infrastructure Gravity & Domain Engineering | Jack Dangerjackdanger.com
- Posts tagged "tech companies"seangoedecke.com
- What is "good taste" in software engineering?seangoedecke.com
- Legal AI Blog for Law Firms | Guides, Reviews & Insights — Augustaugust.law
- Engineering management stuff I learned in 2017. | Irrational Exuberancelethain.com
- How to become a more effective engineernewsletter.pragmaticengineer.com
- Physics and perception. | Irrational Exuberancelethain.com
- Mediumjkebertz.medium.com