In my professional life, I make websites performant and reliable. It's in the job title -- Site Reliability Engineer. I do this using Content Delivery Networks, load balancers, stateless infrastructure, layers of caching, and container orchestration technology. I could think of a few other buzzwords to throw in there, and it probably sounds real impressive to a lay person.
Of course, all that is managed. I abstract myself from managing all of that stuff with just a few text files. Of course, it took significant professional experience to know what I'm doing with those text files, and to be able to arrange these components into a stable infrastructure. And I derive great satisfaction from being able to help create something awesome. And I'm pretty good at what I do, according to my boss and our uptime graphs. I'm not at liberty to share such data so broadly, but I can illustrate this roughly in a graph...
So naturally, since my day to day is spent in the public cloud, using all these wonderful things that have enabled small-time companies with limited upfront budgets to build ultra-reliable, globally distributed websites and services with just a few text files, my personal infrastructure should be built the same way, right? I should be using the trendiest web frameworks, JAM stack, serverless, Cloudflare, all managed using the latest Hashicorp offerings.
I suppose this is my way of maintaining work-life balance, while still exercising some of my skills that I use in a professional setting. I find it relaxing to shift paradigms. I love my job and my work, but I can't really decompress if I just go from writing YAML files at work to writing YAML files at home.
Likewise, I'm never going to roll into work one morning and say "hey y'all, let's ditch this microservices thing and write a bunch of Perl CGI scripts!"
...I just thought of a really funny April Fools prank.
Tags: meta, sre, tech, work