Nice writeup on half an idea. Now, time for some release engineering. How do you give good coders free (enough) reign while keeping tabs on the stupidities of the lesser ones?
In a startup, it's acceptable for service to be accidentally down for short periods while the geniuses running the show fix their latest cockup. In large companies, it isn't. How do you get the best of both worlds?
It is not by removing all safety interlocks. Sysadmins, especially good ones, can tell you in excruciating detail why not. Most programmers are not very good sysadmins, or at least not as good as they might like to believe. Coincidence?
In a startup, it's acceptable for service to be accidentally down for short periods while the geniuses running the show fix their latest cockup. In large companies, it isn't. How do you get the best of both worlds?
It is not by removing all safety interlocks. Sysadmins, especially good ones, can tell you in excruciating detail why not. Most programmers are not very good sysadmins, or at least not as good as they might like to believe. Coincidence?