It has just happened. Inside, I knew I would need to evolve into a different kind of engineer, I was shyly overlooking what projects not related to my work were delivered, the importance of how those compared to mine, and how company-impact were systems used by many and not just by myself. I was eager to explore new concepts, techniques, mechanisms, frameworks and politics. The opportunity arose, and I understood it would have changed my life completely and it prompted in front of my eyes that I could restart and begin a new career path. I'm still a vertical Database Admin but I shifted left (or right) into another path. I discovered more interesting systems and concepts in the last two years as an SRE Engineer Manager than in the last years as a DBOps, where I strived to learn but I didn't run any relevant project. In my current job role, I have many opportunities to learn, share, and interface with others and I really want to catch the experience that will draw my future.
Therefore, I began to build my SRE pillars and I decided to read the Site Reliability Engineering book written by SRE Engineers years ago. These posts are not intended to replace the book but these will be my thoughts on the book's paragraphs and sections. I want to take you, readers, into my journey to explore what would be an SRE.