4 ms·
A side effect of deciding systems engineers can be replaced by devops. In reality, you want both. A good systems person can save you a ton of money.
by _jal 5y ago
A side effect of deciding systems engineers can be replaced by devops.
In reality, you want both. A good systems person can save you a ton of money.
- ithkuil 5y agoA nice approach is to staff a DevOps team with people from diverse backgrounds; some more towards the system side of the spectrum and some more towards the dev side of the spectrum. As long as everybody knows a little bit of the other side. This helps ok avoiding a culture where devs "throw some code over the fence" and sysops people just moan that devs are careless and/or that they should do things differently, but without a clear way of showing exactly how differently things should be made (and also without a clear understanding of what devs ended up choosing the way they choose)
- bradknowles 5y agoWho does DevOps teams anymore? Don’t you know that all devs should also be ops, and you can cut your staff in half? Seriously, some employers I’ve know seem to take exactly that approach. Just fire all the ops guys, and tell the devs that they’re now going to be doing DevOps.
- ithkuil 5y agoOops I clearly didn't mean a dedicated DevOps team; I mean a team that develops and runs a product, what DevOps originally meant (and not the glorified developer tools team that often people have nowadays with that name)
- waynesonfire 5y agoDevops developed and ran product? Never heard of that. What disconnected manifesto did you read?
- ithkuil 5y agoIs the word product rather than service that bothers you or the fact that DevOps develop and operate?