First screen, captured .
346 points by amortize | 72 comments
Blog post by Sujith Jay Nair on how staff engineers on platform teams find what to build next using signals from systems, users, organization, and industry.
502 points by todsacerdoti | 226 comments
Blog post by a Google Senior Staff engineer explaining why he prioritizes long-term systems stewardship over high-visibility spotlight work, responding to Sean Goedecke's essays.
109 points by CarefreeCrayon | 91 comments
346 points by amortize | 72 comments
Blog post by Sujith Jay Nair on how staff engineers on platform teams find what to build next using signals from systems, users, organization, and industry.
551 points by simonebrunozzi | 187 comments
A GitHub-hosted Markdown book by Zach Goldberg, The Startup CTO's Handbook, covering essential skills and best practices for leading high-performing engineering teams.
458 points by Improvement | 130 comments
A personal blog post by a software developer reflecting snarkily on one year working at a large enterprise after a decade in startups and SMEs.
369 points by UglyToad | 199 comments
Blog post by Eliot Jones explaining how PDF parsing should work per the spec, covering headers, cross-reference tables, object offsets and trailers, and its real-world pitfalls.
343 points by zzxcvb | 153 comments
Routledge product page for the 2nd edition of The Garbage Collection Handbook by Jones, Hosking, and Moss, a book on automatic memory management.
491 points by kmelve | 344 comments
Sanity blog post in which a staff engineer recounts six weeks of using Claude Code for development work, noting first attempts are mostly garbage.