Comment by mpalmer

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.