- Developing infrastructure is just like developing a product. There are users who have needs that have to be met.
- DevOps is a mindset, not a function or a role.
- You’re always looking to add automation where it’s needed.
A typical day at Zivver
Times are a-changing with this pandemic, so we had to adapt to a new(ish) way of working remotely. You start your day with the typical stand-up team chat where we look at what’s in progress and what we can do to move them forward on the board.
You then start your day. Sometimes, you are what we call “DevOps of the day”. In this case, you are first in line to help the dev teams who need it, you’re responding to monitoring alerts, and perform routine operations on the infrastructure. The other days, well it’s about solving problems for whoever is running things on the infrastructure: automation, upgrades, infrastructure evolution initiatives, as well as tooling to help our dev teams do the best work of their lives and focus on what matters: our users & customers. Later during the day, after a couple of code reviews for your teammates, you sit down with some developers to understand why they struggle with their builds and test environments, so that next sprint, the team can come up with a solution that allows them to have a shorter feedback loop on their work. It’s already the end of the day, and all your merge requests were approved so you merge them and disconnect until tomorrow!