Managers who "vibe code" are the fitting punishment for the developers who named themselves "DevOps" after believing that they could do without system administrators.
I don't know any developers who believed they could "do without" sysadmins. I know of many who did both roles because their teams were too small to differentiate. (And sometimes that was due to managers who have probably moved on to vibe coding....)
There's nothing more that a "full stack developer" wants to do than drop a software project for a couple of days while they diagnose problems with a samba share only to end up replacing a faulty network card and oh wait where was I with that project....
But DevOps originally meant applying software development techniques to operations: repeatable system deployment and configuration by scripts that are kept in version control, with tests. (It makes sense when you're an op in charge of a data centre with dozens, maybe hundreds or thousands of machines.)
Questo sito utilizza cookie per riconosce gli utenti loggati e quelli che tornano a visitare. Proseguendo la navigazione su questo sito, accetti l'utilizzo di questi cookie.
pgo
in reply to Marco d'Itri • • •dev by accident...ops!
Klaus Frank
in reply to Marco d'Itri • • •Elena ``of Valhalla''
in reply to Marco d'Itri • •Oblomov likes this.
Oblomov reshared this.
Khleedril
in reply to Elena ``of Valhalla'' • • •Elena ``of Valhalla'' likes this.
"Mutant Rob" Robert Rothenberg
in reply to Marco d'Itri • • •I don't know any developers who believed they could "do without" sysadmins. I know of many who did both roles because their teams were too small to differentiate. (And sometimes that was due to managers who have probably moved on to vibe coding....)
There's nothing more that a "full stack developer" wants to do than drop a software project for a couple of days while they diagnose problems with a samba share only to end up replacing a faulty network card and oh wait where was I with that project....
But DevOps originally meant applying software development techniques to operations: repeatable system deployment and configuration by scripts that are kept in version control, with tests. (It makes sense when you're an op in charge of a data centre with dozens, maybe hundreds or thousands of machines.)