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
- Mistakes engineers make in large established codebasesseangoedecke.com
- How I Find Problems to Solve as a Staff Engineerlalitm.com
- LLMs are eroding my software engineering career and I don't know what to do – the human in the loophuman-in-the-loop.bearblog.dev
- Software Engineering fundamentals matter more than everrhonabwy.com
- On becoming competitive when joining a new company – Ludwigludwigabap.bearblog.dev
- AddyOsmani.com - 21 Lessons From 14 Years at Googleaddyosmani.com
- How To Do Lessalexturek.com
- Stevey's Google Platforms Rantgist.github.com
- AI is removing the middle class of software engineeringblog.florianherrengt.com
- How I ship projects at big tech companiesseangoedecke.com
- Posts tagged "tech companies"seangoedecke.com
- Writing an engineering strategy. | Irrational Exuberancelethain.com