A Slightly Noobish SRE

When I began this blog, I had never even considered the idea of doing this but I've decided to migrate blog over to my own website. Oh yeah, and also, I now have a website.... guess I should have lead with that. Anyways, to make a long story short it all sort of fell into my lap and so, he we are. My first post "SRE: Gathering Intel Like 007" is now up and can be found at  derrick-elliott.com/noobishsre . Just warn you, it's still under construction and more or less a "minimum viable product" at this point. I guess you could consider it a soft opening. Over the course of the next couple weeks, I will be migrating the rest of my posts over to the new site while I finish up the rest of the site. Also, any feedback regarding the new site is greatly appreciated. Thank you and enjoy! Also, sorry for the profanity up top and for those offended, admit it, you thought it was funny too.

To preface, this post will be divided into two parts one of which will focus on a "theory" aspect of Site Reliability Engineering and the other will focus on creating a PowerShell module, adding existing scripts to it, and interacting with the module via the shell. So, without further adieu, let's get into this. The Debate In recent months, now that I've started to get acclimated with my new role, I've started to focus on learning more about the concepts behind SRE. The fact is that SRE covers a fairly broad spectrum of potential responsibilities in a role. Some are geared towards web, some systems, some network only, some the entire spectrum. With that in mind, there is a reoccurring topic that I've been running into in regards to the world of SRE. SREs with a background in Systems (SysAdmin, Desktop Support, etc) make the best SREs. Out of curiosity, I did a little research on the areas most SREs come from. It boils down to two of areas of IT,  Systems a...