Why I Ignore The Spotlight as a Staff Engineer - Lalit Maganti
lalitm.com · 2,281 words · saved by 3 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
saved by
related reading
- How I Find Problems to Solve as a Staff Engineerlalitm.com
- Hey, N00b, We Didn't Hire You to Complete Tasksnewsletter.kentbeck.com
- Don't End The Week With Nothingtraining.kalzumeus.com
- AddyOsmani.com - 21 Lessons From 14 Years at Googleaddyosmani.com
- Staff Engineer Behaviors: pt. 2 Breaking the ceiling into Staff Engineeringlevelupsoftwareengineering.substack.com
- #define CTOblog.gregbrockman.com
- Stop just using “Frontend” or “Backend” to describe the Engineering you like - Michelle Limmichellelim.dev
- Posts tagged "tech companies"seangoedecke.com
- Inside Stripe’s Engineering Culture: Part 2newsletter.pragmaticengineer.com
- Infrastructure Gravity & Domain Engineering | Jack Dangerjackdanger.com
- Inside Stripe’s Engineering Culture - Part 1newsletter.pragmaticengineer.com
- What is "good taste" in software engineering?seangoedecke.com