Introduction

Thought I would quickly go over the key principles of Site Reliability Engineering (SRE) and why they matter. Even though these days I am not working in the title, I wanted to address the theory side of things and how this shapes my actions as a Platform Engineer.

My previous role, I was an SRE Architect. And for full transparency, the reason I left was because of economic concerns. The time I was there, the sales pipeline seemed to have dried up, and I was not sure if I wanted to weather the storm in a consulting company that often let people go for being on the bench too long. NetDocuments has been a great change to that uncertainty, and I am indeed, happy to be here.

Introduction

I know that I tend to talk about AI, and “Vibe” Coding. I use it as part of my role and have a deep interest in AI. Sadly, my new blog seems to have been taken over by blogs posts talking about AI and Artificial Intelligence.

And that is because I am genuinely excited about AI. It really has an amazing potential to automate a lot of the workflows in our life and give us a better, less work oriented life so that we can focus on passions, art, creative endeavors, hobbies, and the things we often find ourselves “working” for. After all, in my case, I work to live rather than live to work.

Vibe Coding: Is Making Me Crazy

The image here and in the title is an interesting one. A fundamental part of my blog is the unique structure i am using. I’m wiring these posts as what I would call “Blog as code”, or using a tool known as hugo to put the blog posts into easily creatable and manageable Markdown files. In other words, I don’t want to spend too much time formatting, and would rather just have a couple of Markdown files that i am managing, put into source control in git, and then automatically deployed out my site.