slop

Lost me at “printing press and the loom”

What’s gone is the tearing, exhausting manual labour of typing every single line of code.

That’s never been the “exhausting” part. It’s the VALUABLE part.

The architecture, the trade offs, the product decisions, the edge cases that will bite you at 3am.

Being involved in thebcode at the line-by-line level is HOW you discover and make all these decisions.

I can be the architect without the wearing act of laying every single brick and spreading the mortar. I can design the dress without the act of cutting and sewing each individual piece of fabric.

Maybe YOU can, because you’ve got X years of experience actually DOING those things that you’re now automating away. Newcomers to the industry won’t, and we’re collectively gutting their ability to learn these things.

But I can do all of this with the experience on my back of having laid the bricks, spread the mortar, cut and sewn for twenty years.

The longer this all goes on, the more these skills are going to actually vanish, and NOT just among newcomers. These skills WILL stagnate and die in an experienced engineer, if you don’t exercise them.

Finally dedicating more time of their craft to the art they conceive, not the sweat of the forge.

Dude should check out the WEALTH of channels on YouTube that depict the state of modern blacksmithing and machining. Bad analogy is bad.

We have the chance again to get rid of useless complexity and keep working on the true and welcome complexity of our ideas, our features, our products. The complexity that matters. The complexity that is actually yours.

Dude really just hates bullshit JS frameworks. So do I. So does everyone who uses them. AI isn’t giving us a “chance” to get rid of them, we always had that option. Many of us were choosing it years ago. I convinced my current team to drop jQuery in new code about 8 years ago (andbl not replace it with some other framework), shortly after joining. We’ve never looked back. Didn’t need AI to do it.

We, as an industry, looked at the genuine complexity of building software and instead of sharpening our thinking, we bought someone else’s thinking off the shelf.

Dude… talk about cognitive dissonance. That’s not a description of development within frameworks, that’s a description of agentic development. Except, you’re not “buying someone else’s thinking”, you’re buying a statistical approximation of thinking that doesn’t actually think, or even know what thinking is.