We should have just said: “Hey, developers should deploy their own code.” More than that—they should also be responsible for keeping it running. They should monitor it, respond to issues, and use their programming skills to automate deployments so they’re safe, repeatable, and easy for the team to use. Production-minded developers (who are part of the team!) should do a little extra work to make things better for everyone. This was the correct mindset—a necessary shift away from isolated ops teams managing production without developer participation.
When cloud services arrived, this shift became even more natural. Spinning up a server was no different than calling an API. Infrastructure could be programmed. It could be versioned. It could be tested.
But then we made a terrible mistake: we gave it a name—DevOps.
Suddenly, developers who were good at working with production systems were given a new title. And as soon as “DevOps engineer”
...
Originally, DevOps was about trusting developers with production. But modern DevOps teams operate on the belief that developers can’t be trusted with production
...
So what did creating a “DevOps” role actually get us?
It pulled production-minded engineers off their teams and stripped those teams of both the interest and the permission to manage their own production environments. We ruined the idea of DevOps by formalizing it.
P.S. Platform Engineering is the same story. In the words of Yogi Berra, “It's déjà vu all over again.”
Спиралька...
In retrospect, DevOps was a bad idea.
Ну и да, аргументов "за/против" такой специализации много: сложность и развесистость предметной области (уже даже среди девопсов есть свои специализации), рост компании и необходимость унификации внутри нее (как бы я ее не бухтел на нее) и тдтп. Все это неизбежно ведет к появлению новых "профессий".
Интересно, что нас ждет дальше?
Какие новые специальности уже наклевываются?
#holywar