Do not bother reading this.
The author could have written a rather incisive 800 words on this if he'd really tried.
But I will not read 2500 words of redundant, repetitive slop. It's really bad writing.
There is no pacing or conclusion to speak of. It's sort of just a loose list alternating between upsides and downsides, punctuated by the usual bullshit list-y ad-copy summations:
The build cost collapsed, the alignment cost rose, the thinking time disappeared, and the productivity gains got captured by output volume rather than output quality.
It's really telling.
> the thinking time disappeared
It did not. The author decided against spending time thinking. Nobody is following him around whacking him on the head if he blocks off tomorrow morning to go heads down on something. At least, I don't think they are?
A tiny bit of project management discipline can go a long way.