HN Explorer

Ask HN: Is devops finally over?

2 points by _hyn3 ↗ HN
When I want to develop, I don't want to work on operations, and vice-versa. The context is completely different, and it conflates two completely different mental and authorization models.

Added to this: no one can really define what the devops buzzword actually means. Is it configuration-as-code? developers-doing-operations? or something else entirely?

4 comments

[ 4.1 ms ] story [ 22.7 ms ] thread
verdverm
DevOps is partly about moving code from your editor to users. There are many things that can happen during this process. The main point is automation.

This means some people (DevOps engineers) write code / config systems to realize the process. Then, application developers can take greater ownership over the entire lifecycle of their software, so they end up in the ops side.

When done well, this benefits everyone.

Since software has to move, it is unlikely DevOps, as a practice, will go away.

karmakaze
> When I want to develop, I don't want to work on operations, and vice-versa. The context is completely different, and it conflates two completely different mental and authorization models.

DevOps is about not thinking like this. When developers produce deliverables without a production operational context and 'throw it over the wall' to Ops, it leads to recurring systemic issues. By making developers responsible for what they produce, they feel the pain of their decisions during 'development time' and will learn to make more operational-friendly software.

The other aspects such as automation and coded/immutable configuration came about because of DevOps and is now also part of it.