i don't think grug actually disagrees with you here but takes the position that skill both can't be counted on and doesn't scale.
And this matches my own dev experience cathedrals of complexity pale into comparison that code that's easy to throw away and rewrite to meet changing requirements or scope.
My experience has been that the powers that be generally won't give developers time to rewrite to meet changes in the requirements. Personally as I see it:
iterative development with time to rewrite > cathedral development > "iterative" development without time to rewrite
I think that most teams actually do "iterative development without time to rewrite" so cathedrals of complexity would actually be an improvement.
And this matches my own dev experience cathedrals of complexity pale into comparison that code that's easy to throw away and rewrite to meet changing requirements or scope.