Programming

The first half of the article reads like the dime-a-dozen "if it ain't perfect I'm not using it". You can safely skip it. In the second part, he gets around to his point, which is finally brought home in the summary:

However, especially in software development, it is quite likely that AI-based software development will eventually become the predominant paradigm and the tools will mature. Therefore, it is highly advisable not to ignore AI-based software development even if the tooling is still highly immature. Instead, it is important to follow the evolution and understand the technology well enough to know when the inflection points arrive.

Not sure I follow the DOS/Windows analogy. Unless you spent all your time designing GUIs, a lot of those skills carried over. Especially with the advent of VisualStudio (also intended to replace engineers), you could drag and drop a window layout, double-click a button and continue coding as before. There was a small mental leap necessary to write event-driven code (instead of using a superloop), but that’s an afternoon-long “a ha” epiphany, not going back to school for a new degree. Ditto for MVC-like layering.

And the DOS/Windows analogy is further baffling since Windows-native coding has mostly come and gone. Even “native” Windows apps are typically Electron — web pages captured in a window

Unless the author is saying we must always run to stand still, which they seem to reject early on.

This is a really good read, not sure why its not being appreciated more

Well thought out and well done, thanks for sharing

Guess it just kinda pisses everyone off by not "taking a side" on this set of issues but its a rock solid blogpost for anyone IMO

UNIX schedulers became better and better, and eventually nobody needed to set process priorities and nice levels anymore.

I use nice levels.