...yet when you start looking at how this automated infrastructure works, it turns out to be sloppily crammed together however the webdev happened to work, be v

...yet when you start looking at how this automated infrastructure works, it turns out to be sloppily crammed together however the webdev happened to work, be very brittle, failing every now and then, requiring constant attention and adjustment, non-standarized with tremendous ramp-up time for anybody who needs to take over, and with components mingled together without any separation, so it couldn't be replicated somewhere else. All that because the webdev was learning new Csharp.JS framework like dozen before, being too busy to learn how package system or daemonization or networking or RPC or SSH or push vs. pull architectures worked and what they are good at, or what tools and why a seasoned sysadmin uses for automation. What you really need is not a dilletante armed with sharp and pointy PHP-du-jour, but a system programmer. There used to be such a profession, the guys who wrote syslog, init, bash, grep, awk, libnss, and tons of other goods people today either use without much thinking or don't know existence of at all.