>>35
Holy shit, what a load of horse shit. The problem with that idiot is that he looks at all the fine-grained details and NEVER gets a big picture. He doesn't understand architecture nor organization at all. The only thing he knows is function-level algorithms and trying to peephole optimize. Managing complexity is NOT a difficult task if you've got your shit together.
Many systems NEED to provide a ton of functionality, monitor and report on itself, be runtime flexible and interchangeable without restarting, and all sorts of stuff that requires the addition of complex systems. Fuck, even on a hardware level, mainframe chips easily dedicate 30% of their silicon to monitoring and error conditions. But complexity can be easily managed if you simply develop your code from a big picture instead of trying to collide a mish-mash of shitty "optimized" low-level leaves-before-the-forest algorithms together and pretend it's a working system.