3 ms·
Yes I read the essay. Did you in turn understand what the root cause of that essay is, id est do you understand why "Devops" even came to exist? It exists becau
by Annatar 5y ago
Yes I read the essay. Did you in turn understand what the root cause of that essay is, id est do you understand why "Devops" even came to exist? It exists because "developers" do not want to learn anything about system administration and do not want to learn how to make OS packages, even though ironically, OS packaging was invented for programmers to be able to deliver their software in a standardized, easy way.
RPM can decompress, dearchive, compile, link and automatically test software before packaging, and so can FreeBSD ports. By delivering their software as OS packages, none of this "Devops" nonsense would have to exist in the first place, and frankly it is utter nonsense, hacked-up mess we are in because of it.
Packaging is the answer. And it's much simpler than all these overcomplicated "CI / CD" pipelines.
That's the core problem in that essay. The rest are symptoms of this root cause.
- detaro 5y agoDevops is agnostic to which tool you use. The same ideas apply regardless if you use RPMs, Docker containers, VM images, ... as the format to deliver apps. (remember, the term is from 2009, and that was just when the catchy label was attached, not when people started doing these things, I'm sure good teams did things the label is appropriate for in 90s too)
- Annatar 5y ago"Devops" is nothing more than making "developers" responsible for supporting the mess they "release", because the model of them just shrugging off all responsibility for support, and the sysadmins (2nd level support) being stuck with the fallout was unsustainable. That's the long and short of it.