Management and false certainty
Wow, the author of this seems to have an incredibly inflated sense of the value of his or her opinion, and seems to have very hostile preconceived notions of teammates’ errors and shallowness of their reasons for defending their choices.<p>Not to mention that this part, at least, seems completely wrong,<p>&gt; “But an even slower way to uncover problems than argument is implementation.”<p>Nope. Argument and architectural documents invite all manner of bikeshedding, often wasting time when you could just implement things and adjust the parts that end up causing problems.<p>This is especially critical for taking a YAGNI approach. Architectural designs are such a slow waste of time that ends up leading you down a path where you don’t need various abstractions or extensibility hooks for reasons that only become clear after getting a minimal prototype going, looping in business team feedback, and seeing what fails or works.<p>Basically, most arguments (in the way the author means it) are a really irritating form of premature optimization, and just implementing a first bad version is way more efficient.