From Gatekeepers to Enablers. The story of a fictional company’s SRE journey towards engineering autonomy, more productivity, better compliance and, happiness!

Linkedin described five stages of SRE , the second one being the gatekeeper.

Continue reading From Gatekeepers to Enablers

This is the tale of my imaginary company. Stay tuned!

While I was creating a blog post about how to speed up engineering teams to deliver more value to the end-user, a friend of mine shared an idea: linking that story to a different one I was planning to write and taking the opportunity to use the same fictional characters.

Continue reading An imaginary tale of a growing company

Imagine you are in a remote meeting using terms like SLI, SLO, or SLA, and your kid asks you what it means? How would you explain it to them? Or maybe you need to explain it to your boss or a colleague. In this article, I will try to put SLI, SLO, and SLA in a way even your kids would understand… maybe.

If you are reading this, you probably have been in a situation where you had to explain these terms to people that are not familiar with them. But if you haven’t, I can guarantee that you will. These terms are really simple but at the same time very easy to misunderstand.

Continue reading SLI, SLO, SLA explained in a way your kids will understand... maybe

Companies are adopting SRE, the challenge is understanding what part of SRE they are doing - or if it is SRE at all for the purists

Every once in a while, a new concept appears in the software industry. People start talking about it, making presentations, writing books and even consulting. Everyone seems to be doing the new fancy thing. But even if everyone is talking about it and doing it, are they talking about the same and doing the same?

Continue reading SRE, SRE everywhere

Continuous integration is a software practice adopted widely across the industry, but sometimes it is adopted and implemented without truly understand the advantanges of it and how to prevent common pitfalls. This article goes through some of those pitfalls so we can prevent doing it next time you adopt Continuous Integration.

Continuous Integration is a software development practice where members of a team integrate their work frequently, usually each person integrates at least daily - leading to multiple integrations per day. Each integration is verified by an automated build (including test) to detect integration errors as quickly as possible. Many teams find that this approach leads to significantly reduced integration problems and allows a team to develop cohesive software more rapidly. by Martin Fowler here.

Continue reading Continuous integration - If you don’t know what you’re doing, don’t do it