I wonder how much of the LLM-for-coding hype is because the last 15 years in mainstream coding veered ever more enterprisey layer cakes that took all the fun out of programming

@thomasfuchs probably about 99%.

Of course people are going to turn to these things when the last 20 years of programming industry has relentlessly added layer upon layer of shit, and actively fought any attempt by developers to actually be proud of their work.

@thomasfuchs I was thinking the same thing earlier today: what’s another (masssive) layer of indirection/abstraction when you’re already so deep in it?

@thomasfuchs And somehow writing thousands of words of .md files pleading with an inanimate object to be less wrong is more appealing.

Okay, I’ve done EJB, I can see that.

@thomasfuchs This is my take on it too. If your coding is 90% boilerplate, then of course you would like to automate the boilerplate generation. Before LLMs we used other tools. Code generators were popular in enterprise Java for a while.

This is, of course, a terrible solution. Profitable though.

@thomasfuchs The people I've seen who are most enthusiastic are either very junior folks who want to rush everything and cut corners, or very senior folks who haven't really been coding for ages and this is an excuse to play with something.

@thomasfuchs

"But look at all this awesome documentation* I've produced so it is maintainable"

* Which I've not read, can't vouch for, and will be different the next time it is produced

@thomasfuchs

And simultaneously because during the last 15 years, the need for programmers exceeding the need for available talent lowered the bar of entry *so much* that LLMs sound like a tangible alternative to most.