Great Stuff!

That is pretty context sensitive. You're correct that there's no real deep AI use expertise broadly understood to exist at this point (unless you're Steve Yegge?), but if people think they can toss out the engineers with experience in the systems that have been around a while, with junior developers "guiding" changes — that's likely a good way for a business to fall on its sword.

> “We should bear in mind that, in general, it is the object of our newspapers rather to create a sensation — to make a point — than to further the cause of truth.”

Context switching and message passing (synchronous anyway) are the same thing when you consider how rendezvous works.

BLWP instructions seem like this was “meant to be”.

I feel more like a software producer or director than an engineer though.

https://intellectia.ai/news/stock/ibm-mainframe-business-ach...

60% YoY growth is pretty excellent for an "outdated" technology.

Just kidding... That sounds like my journey as well. I had friends in the neighborhood who also had the TI-99/4a. We all had Cub Scouts and Boy's Life magazine listings to key in.

Did you have the data cassette recorder? We used to try to "load programs" from Michael Jackson's Thriller album.

I cannot recall the cartoon, but there was a revelation of "why a character was such a bad actor" (a jerk). And the reply was ironically one of care — "I don't want anyone to miss me after I'm gone".

As if to relieve the pain of loss they wanted others to feel relief.

I wish I could recall the cartoon and the author.

It's really not bad, and you can use it for scripting like sed, but it's clunkier.

lol?

But, if you squint, great API design is a bit like embedded domain specific language design as well.

I think there's room for both.