The problem with this article implies a bureaucratic division of labor when developers are often the sysadmins. Any upcoming startup can't afford to be resistan

The problem with this article implies a bureaucratic division of labor when developers are often the sysadmins. Any upcoming startup can't afford to be resistant to change--and things will break, but nobody will know more about the software than the developer. This kind of thinking reminds me of the way the enterprise software world is run, and they're not exactly renowned for quality, either. I've found that great scaling is the result of sending sysadmins to work along side developers, and having developers work with production/testing to learn about each's side struggle. It's not R&D vs Operations, they're on the same team! If you're building a house, you might have architects and builders, and while the architect draws the blueprints, the actual construction people are just as important since they have an equally good understanding of the other side, such as applying the materials in good form.