You have to beat the models at something
In 2025, I wrote that software engineers ought to be assessed by “value over replacement”: not how much money they made for their company, but how much they…
In 2025, I wrote that software engineers ought to be assessed by “value over replacement”: not how much money they made for their company, but how much they would have made compared to the average engineer in their position. I’ve always found it vaguely silly when engineers put “built a product that made $X” on their resumes, when they just did the JIRA tickets that came across their desk. Today, value over replacement is even more important. A replacement-level engineer in the 2010s was fine: maybe not worth promoting, but still worth paying, because writing code had a high fixed cost. Now…
saved by
related reading
- AI is removing the middle class of software engineeringblog.florianherrengt.com
- To avoid being replaced by LLMs, do what they can'tseangoedecke.com
- How to fully automate software engineering | Mechanize, Inc.mechanize.work
- Code is cheap. Show me the talk. - nadh.innadh.in
- Your job is to deliver code you have proven to worksimonwillison.net
- How I use LLMs as a staff engineerseangoedecke.com
- We mourn our craft | Read the Tea Leavesnolanlawson.com
- Society's Technical Debt and Software's Gutenberg Momentskventures.substack.com
- claude code is not making your product betterethanding.substack.com
- No, LLM is not going to replace software engineers, here's why – Fang-Pen's coding notefangpenlin.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
- After Automation | Everyevery.to