one can go through a full cycle of the “write code” loop faster than one would go through “suffering the consequences of your own architecture” loop

The implication here is that if you’re on a new code base with no history and a future that might not exist (such as short-term prototypes or experiments), you’re likely to be able to have isolated short loops. If you’re working on a large platform with thousands of users, years of accrued patterns and edge cases, and the weight of an organizational culture to fight or align with, you end up relying on the longer loops to inform the shorter ones.

Did I expect to read a piece applying Hartmut Rosa to software engineering? No. Did I expect that piece to then be very very good? Also no.

Fred Hebert explains why the acceleration of code generation by AI does not make everything faster. In fact it may slow things down.

https://ferd.ca/software-acceleration-and-desynchronization.html