If you do not act on your DevOps setup, your DevOps setup will act on you. Markus Schünemann, a clever chap, realized that when Lano started to grow like hell. Thankfully he did so early enough. As you surpass 15 developers, things usually get complex and ugly quite fast. Your toolchain gets more complex and your team ends up needing 11 different tools to keep an app up and running.
More people, more dependencies, and you slow down. If you look at it in detail and cluster the reasons why this happens, I usually identify four distinct ones:
- Dependencies on colleagues
- Maintenance overhead
- Ineffective and broken toolchains
- Cognitive load
From all the data we currently have (take the Puppet report, Accelerate State of DevOps or really, anything else), the one solution is developer self-service! It eliminates the dependencies, decreases overhead, streamlines workflows, and allows developers to focus.
Markus first had to feel the pain himself until he built his Internal Developer Platform with Humanitec and the sun was shining again. Another beautiful example is Digital Freightforwarder Forto. They moved from Heroku to Kubernetes and their VP Engineering shares some valuable lessons in this article he recently posted.
I can help you understand that (much) faster. Join me for an interesting webinar on “Developer Self-service: the key to DevOps”. Or join Puppets field CTO Nigel Kersten in May when he talks about the latest data from their State of DevOps Report!
And what do the best teams build to enable self-service? Internal Developer Platforms! I’ve spent a while writing an article to really, really go into the details of how these platforms are set up and work, hope you enjoy it!
Hope all of you are doing well!
Cheers,
Kaspar
