but in the end these networks need to be managed by multiple people. As they said, 'what if he gets hit by a truck?'
(or my fav - I'll get hit by a beer truck on the way to the health food store :)
There needs to be managers who understand the network to the degree that they can make sure it is:
recoverable if anyone leaves / dies /etc
(him being the only one able to change things)
secure but not to the point of being unusable (not flashing configs, etc)
We had engr mgr of unix box who left on vacation for two weeks (to another country). He had not previously let anyone have admin password, and the box then became unusuable after problem (power out maybe, can't remember).
Finally we had to have his mgr tell him to give up the pwd or leave the company.
What would be the ideal setup? I guess that could vary depending on size and people employed in any setup. At least the managers should be trained to not let megalomaniac techies get out of control. On the other hand, if the network is so complicated that only one person can manage it and will crash if he lets someone else in then they need change control, documentation, automated testing, and quite possibly simplification. If he setup a complicated kludge just for brilliancy's sake that only he understands, that is worthless!