How I estimate work(seangoedecke.com)
450 points by mattjhall | 268 comments
Sean Goedecke's blog post on how he approaches estimating software work as a staff engineer, arguing accurate estimation is impossible.
First screen, captured .
Looks similar
Related stories
The future of software development is software developers(codemanship.wordpress.com)
376 points by cdrnsf | 471 comments
A Codemanship blog post arguing that the future of software development still depends on human software developers.
I'm addicted to being useful(seangoedecke.com)
519 points by swah | 265 comments
Sean Goedecke's blog essay on loving his software engineering job because he is driven by being useful, drawing on Gogol's The Overcoat.
Nobody knows how to build with AI yet(worksonmymachine.substack.com)
475 points by Stwerner | 368 comments
Scott Werner's Substack essay arguing nobody yet knows how to build software with AI, drawing on building Protocollie in four days without touching the code.
There's no reason for software to be slow anymore(danluu.com)
592 points by Jach | 442 comments
Dan Luu essay arguing that LLM coding agents make specialized performance optimization cheap, illustrated with optimizing a regex engine for specific workloads.
Software engineers hate code(dancowell.com)
323 points by dfcowell | 185 comments
A blog post by Dan Cowell arguing that software engineers dislike code and prefer writing less of it.
Someone behind the software(karrisaarinen.com)
532 points by tosh | 188 comments
Blog post by Karri Saarinen arguing that good software products carry the experience, values, and perspective of the people who make them.