3 ms·
Is Ops a Bullshit Job?
- deleted 2y ago[deleted]
- 28304283409234 2y agoNo, because the whole is greater than the sum of its parts. And you are the one making it whole.
- sepositus 2y agoNot sure what experience OP has, but I’ve never been on a team of devs who were actually interested in doing anything beyond writing code. It’s typically like pulling teeth just to get them to accept a minuscule portion of responsibility for delivery.
- donutshop 2y agoSame.
- riehwvfbk 2y agoOh, we are interested all right. But doing ops work is career poison to a dev and so it can only be done in exceptional circumstances.
- mmarian 2y agoNot sure why your comment was downvoted since it's true. If developers were told that ops work would lead to better comp, rather than the latest new framework, then they'd gladly learn it.
- altairprime 2y agoAs someone with thirty years of ops work under my belt, I feel compelled to say a few words in reply to this article.
- donutshop 2y agoLet's hear it!
- altairprime 2y agohttps://xkcd.com/1636/ https://xkcd.com/1636/
- skuxxlife 2y agoPart of the problem is that when ops is doing their job well, nobody notices. You get a party when the regular devs ship a big new feature, but no-one really celebrates when you have five nines of availability for the year. Personally I’m a big advocate for devs doing a rotation on an ops-focused team so they better understand the full picture of professional software development. Hopefully they learn that it takes more than code in an editor to create a product.
- channel_t 2y agoI will say that it can definitely very much be a bullshit job if your org structure is optimized for bullshit. Like 80% of QA jobs are the result of hierarchical bullshit pipelines, and certainly no small percentage of dev roles too.