4 ms·
I 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
by twic 5y ago
I 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.