Very amusing article, but fails to nail the two core issues for a showdown
1. Creating excellent systems is hard, especially Complex and/or Realtime systems. The more layers, more integrations, more sponsors, the greater the need to communicate design early on in the cycle when cost of change is lower.
2. Incompetent people will find something to do, rather than finishing the job. The closer to the metal, the more difficult it is to hide.
It’s an easy mistake to strip down the Software Design process like a Daytona track car, when the design problem is the same as it was when Fred Brooks wrote the mythical man month – productivity.
The DevOps approach improves the productivity of developers, and can be applied to Architecture through code generation and automated reverse engineering. Arch-Ops is the next phase not an alternative