4 ms·
Wow that was excellent, very thorough but also easy to read and with minimal fluff My personal take is that DevOps doesn't work (for me, and probably many othe
by brundolf 4y ago
Wow that was excellent, very thorough but also easy to read and with minimal fluff
My personal take is that DevOps doesn't work (for me, and probably many others) because it amounts to context-switching (recently featured on HN: https://news.ycombinator.com/item?id=32390499 https://news.ycombinator.com/item?id=32390499). By being responsible for both Dev and Ops, my time (and my brain) gets split 50/50 into two entirely different sets of:
- Concerns
- Languages
- Tools
- Mindsets
This is both super draining, and counter-productive, for me. If Ops can be made so simple (by a platform team or otherwise) that it doesn't amount to a whole separate headspace, then great, I'll manage instances myself. But as long as it's a whole separate domain, trying to have one foot on each side of the fence is just not going to be workable.
- astral303 4y agoI think real DevOps works here just fine as long as your organization allows the time for deep work. If you are writing application code with 0% of your brain lent to operational concern, you are writing it in a disconnected dream cloud and your organization will have problems that come from it. The answer to context switching is not do it several times per day. The answer is NOT to ignore operational concerns and mindsets. Many engineers pride themselves on having a wide set of skills and enjoy switching contexts, languages, tools and mindsets for variety and to reduce boredom.