3 ms·
> a lot of tasks people try to accomplish are just bad ideas. For most people, the point of config management tooling is to turn all their manual, bus-factor-o
by derefr 9y ago
> a lot of tasks people try to accomplish are just bad ideas.
For most people, the point of config management tooling is to turn all their manual, bus-factor-of-one crufty legacy processes into automated, documented, centralized crufty legacy processes.
Ops people don't want a system that is opinionated or that pushes back to force them to change their process. They want a Turing-complete system, and maybe macros as well, so that they can quickly encode their hairy manual process into a hairy automated process, and get back to all the other firefighting they have to do as ops people.
- peterwwillis 9y agoIn theory, with unlimited resources and fully automated systems, there should be no infrastructure problems to firefight. But probably even with limited resources we shouldn't need to firefight so much if it was engineered correctly. I think about cars and planes, and wonder what life would be like if we needed a team of engineers sitting on the wing of a plane to keep it in the sky when the pilot moves the flaps.
- derefr 9y ago> what life would be like if we needed a team of engineers sitting on the wing of a plane to keep it in the sky It's the world we'd be in if new planes were in such high demand that the number of startups building them totally outstripped the supply of aeronautical engineers, to the point that most new designs only had ~5 man-years of effort invested in them on release, rather than the thousands they get today. Software is really a different world, economically.