Found some insightful bits within this in a general 'principle/discipline of programming' sense, since it's written by an "outsider" yet in the presence of "the OGs"

E.g.

> The task of writing a program ... is traditionally characterized by a specific set of disciplines.

> In essence, the programmer must define some sort of algorithm which will accomplish the objective, then map that algorithm onto the available resources of the computer using a specific set of tools — the programming language.

> Conversion of an idea from its conceptual form into its coded form involves the acceptance of *nearly brutal language restrictions* which result in strict formalization of the process.

> The programmer starts with an idea of WHAT he wants the system to do, then spends hours or months describing HOW it should be done.

> The generally-accepted complexity of this task has spawned some rather elaborate disciplines which reduce the probability of error.

I think the fact that LLMs are "eating up" so much of software development is that software development itself never properly matured. It remained in this form for decades longer than it should've (for various reasons)

Also, writing stories never matured, painting pictures never matured, swindling people out of money never matured, ...