3 ms·
I've both been responsible for hundreds of systems as a full-time job and written software as a full-time job. Over a couple decades the ratio has changed from
by acdha 9y ago
I've both been responsible for hundreds of systems as a full-time job and written software as a full-time job. Over a couple decades the ratio has changed from job to job but I'd also describe my style of system administration as automation-heavy and had been encouraging people to think of the job as writing code to manage systems rather than manual work since around the turn of the century so there was definitely non-trivial crossover even before the DevOps coinage became popular. (And, lest that sound vain, that wasn't exactly something I came up with. It took a long time for the automation community to go really mainstream – HPC was years ahead by necessity)
I won't claim that systemd is perfect or that I'm happy with every detail of its development history but in practice I find it's not something I need to think about very often. That was true of later Upstart releases, too, so I mostly don't get the bitterness some people have: flip a coin and either way we have a nice quality of life improvement over SysV. Yes, Red Hat carries a lot of weight but they also employ a ton of open source developers so it's not like that's unearned.