diff options
Diffstat (limited to 'src/content/post/devops-mindset.md')
| -rw-r--r-- | src/content/post/devops-mindset.md | 35 |
1 files changed, 35 insertions, 0 deletions
diff --git a/src/content/post/devops-mindset.md b/src/content/post/devops-mindset.md new file mode 100644 index 0000000..166d282 --- /dev/null +++ b/src/content/post/devops-mindset.md @@ -0,0 +1,35 @@ +--- +title: "DevOps Mindset" +description: "DevOps - culture, mindset and processes" +publishDate: "3 July 2025" +tags: ["devops101", devops] +draft: false +--- + +## DevOps Mindset + +The first thing you need to understand to become a good DevOps engineer is what DevOps truly is. Being a DevOps engineer means driving change in culture, processes, and mindset. I often say I do *DevOps evangelization*, because the shift in how people think and work is far more important than tools and automation. Without that foundation, no tool will bring real improvement. + +This mindset helps focus on what truly matters. As a consultant, I’ve often been asked about priorities - where a project should invest its main efforts, and what actions will bring the biggest results with the least effort. + +Some books that helped shape my thinking: + +- [*The Phoenix Project*](https://www.goodreads.com/book/show/17255186-the-phoenix-project) - Absolute legend book +- [*The DevOps Handbook*](https://www.goodreads.com/book/show/26083308-the-devops-handbook) - Must read handbook +- [*The Unicorn Project*](https://www.goodreads.com/book/show/44333183-the-unicorn-project) - Modern version of *Phoenix Project* + +These books won’t solve your problems or give you ready-made answers, but they will help guide your decisions. The principles behind DevOps - building healthy work environments, creating well-sized and effective teams - are universal, regardless of the technology or the company. + +Key ideas you’ll find in them: + +- The "wall of confusion" between development and operations teams +- Shift-left approach and continuous feedback +- Blameless culture and continuous learning +- Cross-functional cooperation and shared goals +- Lean thinking and waste reduction +- Security as an integral part of the development process +- [CALMS](https://devops.com/using-calms-to-assess-organizations-devops/) framework +- [DORA](https://dora.dev/guides/dora-metrics-four-keys/) metrics +- [Value stream mapping](https://dora.dev/guides/value-stream-management/) + +The most important takeaway: **DevOps is not about tools**. It’s not CI/CD, it’s not Kubernetes, it’s not Cloud or Ansible. DevOps is a mindset. Tools are just there to support processes. Don’t forget that. |