Looks similar
Related stories
Nobody ever gets credit for fixing problems that never happened (2001) [pdf](web.mit.edu)
722 points by sam_bristow | 243 comments
A 2001 California Management Review paper by Nelson Repenning and John Sterman on why process improvement programs often fail and how to create and sustain them.
There is more to code review than (automatable) detection(adaptivecapacitylabs.com)
142 points by utiiiD | 88 comments
Adaptive Capacity Labs blog post arguing that code review involves more than defect detection that can be automated.
Coding is not solved(blog.alexewerlof.com)
458 points by firstSpeaker | 459 comments
Alex Ewerlöf's opinion essay arguing that AI and LLM coding tools have not solved software coding, drawing on his experience building AI systems.
When the machine boots but the reply disappears(mainbrella.com)
4 points by cs1996 | 3 comments
Mainbrella engineering blog post on designing its backend so retries are safe when a Linux machine is created but the reply to the client is lost.
Why don't more developers “use the platform”?(nolanlawson.com)
304 points by vinhnx | 318 comments
Nolan Lawson blog post examining why web developers often don't "use the platform" and rely on JavaScript instead of built-in browser features.
A decade later, a decade lost (2024)(meyerweb.com)
503 points by ZeWaka | 151 comments
Eric Meyer's personal blog post reflecting on the tenth anniversary of his daughter Rebecca's death on what would have been her sixteenth birthday.







![Screenshot of web.mit.edu: Nobody ever gets credit for fixing problems that never happened (2001) [pdf]](https://hn.urlbox.com/shots/renders/2026/6/12/31f86412-6671-406f-b1af-e0a219ac3803.jpg)




