Free wrong answers.

Good software has always been about deciding what not to build. Cost was one of the mechanisms that enforced those decisions — not always the right one, but on balance it created discipline.

Now that it’s gone, the discipline has to come from taste, from product thinking, from someone asking the uncomfortable question: do we actually need this? The problem is that “we can build it basically for free” is a very persuasive answer. Even when it’s the wrong one.

Jan-Gregor Triebel: Cheap Code Considered Harmful (2026-03-03)

Multiple Dings, Zero Peace.

So that’s my takeaway. If you don’t know what done is, you’re not really delegating work, you’re just feeding the clicker. Just because I can build something now that I couldn’t before doesn’t mean I should.

Adam Gordon Bell: The Universal Paperclip Clicker (CoRecursive Podcast 2026-02-04)

What can go wrong except everything?

All is beautiful and all is good
All the monsters are defeated too

Charlotte Wessels: The Crying Room

Slopucation.

The real concern is for generations of learners who are being robbed of the opportunity to acquire the expertise to objectively discern what is slop and what is not. Even worse, the possibility that experienced folks who use these tools effectively, will feel disincentivised from mentoring and training junior folks in foundational ways, something that was a natural part of societal evolution. And not just with software development, but the wholesale offloading of agency and decision-making to black boxes.

Kailash Nadh: Code is cheap. Show me the talk. (2026-01-30)

E-Kettle.

How did anyone ever live without a water boiler?