I enjoy learning about various aspects of open source projects, especially when they are gaining popularity in the DevOps arena. Designated as "DevOps" projects can be scalable collaborative systems that address a wide range of problems, from messaging to monitoring. There is always something new to explore, install, unwind and explore.
However, DevOps cannot exist without principles. Some of these concepts are obvious truths that took some time to accept. In turn, there are other ideas that help us recognize a lot and go beyond our cognitive biases .
While not strictly speaking DevOps, one of the principles that changed everything for me is Kanban . The simple idea that work should be transparent and streamlined was radical for a chronically multi-tasking person like me. I maintain a clear workflow to this day. The ability not to get lost in tasks was a huge relief for me. In addition, I no longer rejoice in intermediate successes: now I rejoice in accomplished tasks.
To find out what influenced my colleagues, I asked members of the OpenSource.com DevOps team to share their thoughts on the matter:
Which DevOps concept (practice, principle, or model) changed your career?
Alex Bunardzic
Make mistakes faster, make mistakes early, make mistakes as often as you can. Before I delved into this amazing concept, I struggled and worked in vain with the standard waterfall model. My career consisted of a number of unsuccessful projects, and they all began with the thesis "No rejections are allowed!" This is an extremely tedious model that reduces work efficiency and leads to the fact that from one frustration to another, you have to move to the next.
Bringing to life a barrage of quick and violent rejections is the best thing that has happened in my career. Frustration gave way to a feeling of flight. This led to the mass adoption / implementation of TDD practices [test-driven development] and to the realization that TDD is not a "test" , but"DRIVING" !
Catherine Louis
Cultural hacking . I had no idea that there was a name for the method that I (as a partisan) used to change the corporate culture, but then I saw Seb Paquet's video "Ignite Montreal" and was glad that it was not just me who was doing this.
Clement Verne
Continuous improvement . Until I was introduced to the ideas of continuous improvement, I was not looking for ways to grow in my work or career. Constant improvement made me realize what exactly depends on me. I realized that I could challenge myself by learning new things and getting out of my comfort zone. This led me to start contributing to an open source project (Fedora) and then work at Red Hat. It definitely changed my career.
Jason Hibbets
It all started with “The Lean Startup” at my first Code for America Summit . I vividly remember the turning point in my career in 2012. Eric Rees, author of The Lean Startup and member of the Board of Directors of Code for America, was onstage with Tim O'Reilly, talking about code breaking, culture and failures in knowledge testing. My biggest achievement was Introducing The Lean Startup. I downloaded the book and read most of it on the flight home. It changed the way I work and lead a team.
The biggest change I made was the introduction of feedback loops.... This has critically influenced my work style and my team. I shifted my team's habits towards data-driven decision making. We began to exchange information and ideas through feedback loops. We also hold weekly health checkups and continually explore our workflows and hypotheses. In addition, we experiment with new ideas and evaluate these experiments. We hold meetings at the beginning of a task during the work on it and after its completion - this allows us to understand what to do next and what not, so that we can move on.
Willie-Peter Schaub
On my two-month sabbatical in 2018, it dawned on me that the fear of failure was robbing my energy and passion for software development, and I loved that career. I realized that mistakes are not a tragedy, but a tool for innovation, collaboration, and continuous learning that fuels DevOps. And this realization has become a key moment in my career. Transparency of collaboration, progressive exposure, hypothesis and test-driven development, and CD techniques - all of these practices create opportunities for early failure, validation and adaptation of the solutions we are working on (and our careers).
Your turn
DevOps can teach you a lot, even if you never open a terminal or any program. So I ask you the same question:
Which concept from DevOps has had the greatest impact on your career?
Please share your thoughts in the comments.
Learn more about how to get a high-profile profession from scratch or Level Up in skills and salary by taking SkillFactory's paid online courses:
- DevOps course (12 months)
More courses
- - (8 )
- UX- (9 )
- Web- (7 )
- Machine Learning (12 )
- Data Science (12 )
- (9 )
- «Python -» (9 )