4 ms·
> every team, composed only by SWE, is responsible for the whole code lifecycle, from inception to deployment to maintenance to decommission I think this is th
by robertlagrant 5y ago
> every team, composed only by SWE, is responsible for the whole code lifecycle, from inception to deployment to maintenance to decommission
I think this is the original thesis for DevOps.
- darkwater 5y agoYes, absolutely, but it's not actually widely implemented. Orgs does "DevOps" but they are just automating/writing as code some things that previously were done manually by Ops/SysAdmins. Now we have DevOps roles doing that same work but with other tools (Terraform, Cloudformation etc), much more automation, less gruntwork and toll but STILL used as "developers IT" nonetheless.
- robertlagrant 5y agoNot disagreeing :)
- nonameiguess 5y agoThis isn't true at all, though. Many organizations, especially smaller ones, seem to have taken it this way. Everyone is responsible for everything. But that wasn't the DevOps thesis. The idea was for eliminating silos in the sense that dev and ops would talk to each other continuously throughout the software lifecycle, with developers understanding operational challenges and creating software that didn't just meet functional requirements, but was easier and faster to deploy, change, rollback, and troubleshoot. Ops would understand the pressures of development and create automation systems catered to the specifics of their software stack. It wasn't supposed to mean no more division of labor. Division of labor is a key innovation in human society that enables civilizations to exist. It was supposed to mean the teams in different categories of labor interact throughout and consider each other's needs, and not throw shit at each other over a wall and only ever interact through a ticketing system.
- twic 5y agoI believe that it was supposed to mean no more division of labour, and i believe that based on conversations with people who were early adopters of it ten years ago. This waffly "breaking down the silos" stuff is a later redefinition, i believe reacting to the fact that the original meaning was extremely unpalatable to existing organisations, with existing employees and hierarchies who would be severely disrupted by it.
- darkwater 5y agoBut I still challenge the fact that it can really work well for normal performers and not only top notch developers. Taking care of all the phases of a software lifecycle is not an easy task, it has a big enough cognitive load. I understand that this is supposed to be done in (small) teams, but within those teams you still need some degree of separation of labour, you cannot have everybody having wide and deep knowledge of everything software. Well, you can do it, if you are Google and the like and set the bar for hiring really, really high. But that doesn't apply to most organizations and engineers. Not all of us are wicked smart.
- vajrabum 5y agoHere's a link to an interview with Patrick Debois who is one of the two guys who came up with the concept of DevOps. https://blogs.oracle.com/javamagazine/how-dev-versus-ops-became-devops https://blogs.oracle.com/javamagazine/how-dev-versus-ops-bec... From Patrick Debois in the interview "Later, I saw a talk by Jean-Paul Sergent about developer (Dev) teams and operations (Ops) teams working together." So no, breaking down the silos was baked in from the beginning.
- robertlagrant 5y agoYou're missing the fact that a team can have different specialisms. It doesn't have to be each individual can do everything.
- m1keil 5y agoThe original thesis was better cooperation between developers and sysadmins (ops). It didn't focus on trying to make operations redundant or transfer every sysadmin into a SWE.
- thesuperbigfrog 5y agoIt is. The team that writes the code should also deploy the code and get paged in if there are problems in production. That creates a tight feedback loop that requires developers to learn and manage the whole stack, code defensively, and test enough to be confident to deploy to production. Didn't test your code enough? You will be paged in the middle of the night to fix it. It creates a strong incentive to make good decisions because you will be living in the mess you create.
- cestith 5y agoIn those cases, though, it's usually a team with some Dev people who know or can learn some Ops and some Ops people who know or can learn some Dev. It's not just laying off all the sysadmins, network admins, stack architects, and all then letting the developers freefall until they find a way to right themselves.
- cbushko 5y agoAnd this only works if your Ops team provides good tooling for deploying, logging, monitoring and alerting. I have heard of companies deciding to do 'devops' and it turns into a free for all of dev teams having to handle/build things end to end. Everyone loses in that scenario.