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
- Your job is to deliver code you have proven to worksimonwillison.net
- To avoid being replaced by LLMs, do what they can'tseangoedecke.com
- The Eternal Sloptember | the singularity is nearergeohot.github.io
- How to keep thinkingseangoedecke.com
- Thoughts on the job market in the age of LLMsinterconnects.ai
- How to fully automate software engineering | Mechanize, Inc.mechanize.work
- Malleable software in the age of LLMsgeoffreylitt.com
- What We’ve Learned From A Year of Building with LLMs – Applied LLMsapplied-llms.org
- Don’t Outsource Your Thinkingteltam.github.io
- claude code is not making your product betterethanding.substack.com
- Software Engineering fundamentals matter more than everrhonabwy.com