Earlier quoted context omitted.
The problem with a careful but non-methodical approach is that it requires the programmer to correctly determine the stability value of their design. We often overestimate the importance of architecture on stability, or worse, architect something that is harder to maintain than the naive solution. With buggy ship-it-now software you have a known bounded risk - bugs will occur in some cases but the software will ship…
There are more choices than "ship-it-quickly and fix bugs later" and "over-engineer something complicated that ships later". There are _lots_ of good practices which reduce the (potential) bug count without making things more complicated -- indeed, good practices serve to reduce complexity in design and architecture. Selecting the right data structures and algorithms, server-side validation, making proper use of your…
It is abundantly clear that GP is roughly describing two ends of a spectrum, not enumerating every possible option.