Nothing too recent that I know of but a couple of discussions:

https://spiderwebforums.ipbhost.com/topic/26438-good-first-g...

https://www.gog.com/forum/general/what_are_your_favorite_spi...

> We'll have to discover where to draw that line in education and training.

I'm not sure we (meaning society as a whole) are going to have enough say to really draw those lines. Individuals will have more of a choice going forward, just like they did when education was democratized via many other technologies. The most that society will probably have a say in is what folks are allowed to pay for as far as credentials go.

What I worry about most is that AI seems like it's going to make the already large have/not divide grow even more.

that's actually what I mean by we. As in, different individuals will try different strategies with it, and we the collective will discover what works based on results.

It's a bit ironic that the "soft" skills are becoming the hard skills nowadays. A lot of the AI buzz these days is around PM's, Data Scientists, etc. who now have the tools to code "well enough" and are attractive due to their people skills and/or other skillsets.

Not to say this is an objective analysis, just observing the subjective trends.

For folks who scan code bases based on the front of lines, it makes it easier to grok. Also helps with deleting and inserting lines (similar to leading or trailing commas in lists).

> Vibe engineered

While I'm all for vibe coding as appropriate, there's a lot of humor to be found it calling it engineering. :D

this is not something I came up with, Simon wrote it and I liked the differentiation between "vibe coding" where there is less effort

for this case project I think I would actually go back and say it's vibe coded, but I didn't want to just call it vibe coding because I did spend time going back and forth and directing the agent

https://simonwillison.net/2025/Oct/7/vibe-engineering/

Interesting distinction. I've previously heard vibe coding described as "vibe prompting, but you actually do some work." That aside though, I just call what you're describing as coding with AI.

coding with AI is coding just as much as coding with VSCode is coding. you decide which parts you get help from a given tool and which you don’t. end of the day, it is all coding and “coding with AI” sounds as silly as “coding with keyboard / microphone”

The first part is exactly my point, but the latter is nonsense in my book. You cannot ask VSCode (pre-AI) to write a program for you. It's akin to doing math with AI vs. an Nspire CAS. There's no reason to think you need to respond to those who shame vibe coding with claims that we shouldn't differentiate our tools, but we also shouldn't just say it's all the same. We wouldn't claim that about farming with a laser-powered weed killer compared to farming with a horse-drawn plow.

I suspected it needed to be directed with a specification to call it vibe engineered

Fair. Though it seems that half of engineering is just giving a respectable name to whatever actually works.

For software, but that's a well trodden path at this point. I've seen a few projects that are actually "vibe engineering" outside of software on the 3d modeling side so the terms are confusing.

I've been a fan of Design-Assisted Developer or DAD

What is funny about it?

Unless social justice is really seeing a renaissance, it's indeed far more likely that "things are getting expensive and I don't want to pay $6+ for as many cups of coffee as I used to" is the main cause.

While I say this somewhat in jest, frugal is just cheap but with better value.

For the fundamentals, sure, but many of the top sellers are going to be on things like React, Next, etc.

And in ten years after react is forgotten about, there will still be companies actively hiring Java developers

See you in ten years! We're a hop, skip and a jump from one click automated conversion from every legacy Java app to web and electron desktop compatible code and we can just retire Java entirely. in 2025, Java is not the most performant. It does not run in the most places. it is not the easiest to write or reason about. its advantage over anything else is momentum and it's losing that too.

React is just a formalizatio of a UI update pattern that exists in every app ever made except the ones that are bad. Source: written a lot of java and nobody is currently paying enough to make it worth doing again.

> And in ten years after react is forgotten about, there will still be companies actively hiring Java developer

In ten years you'll see greybeards complaining that new kids don't know shit about React fundamentals.

> In ten years you'll see greybeards complaining that new kids don't know shit about React fundamentals.

Nah you won't. Js frameworks comme and go all the time

> Nah you won't. Js frameworks comme and go all the time

React was released 12 years ago, and since then a few React clones popped up as well such as Preact.

React occupies a very similar place today as angular did back in the day, and angular is on life support, if that.

I don't know what argument you think you are making. React was released in 2011 whereas AngularJS was released in 2010 and Angular2+, what we actually call Angular, was released in 2014.

So your counter examples of popularity are projects what at best started out at the same time as React but unlike React winded down in popularity.

After over a decade l, React is not only the most popular framework by far but also is the support framework for a few of the top 10 frameworks.

So what point did you thought you were making? That React managed to become the dominant framework whereas your examples didn't?

Yes, that would be my point (the courses will be outdated that once sold well).

Junior engineers are the usual comparison folks make to LLMs, which is apt as juniors need lots of oversight.

Author is Peter Norvig, who has definitely done “something useful” when it comes to AI. He’s earned some time for play.