$ cat post/reflections-on-the-early-days-of-sre-in-a-remote-first-world.md

Reflections on the Early Days of SRE in a Remote-First World


May 17, 2021 was just another day for me, a platform engineer navigating the shifting sands of modern infrastructure. The era of remote work had settled into a new normal, with tools like Zoom and Slack now integral to our daily grind. Yet, amidst the comfort of my home office, I couldn’t shake the feeling that something in tech was quietly transforming.

The Rise of SRE

One thing that caught my attention was how SRE roles were proliferating. My company had just hired a full-time SRE to join our devops team, and it felt like this role was becoming as common as a CI/CD pipeline. Internal developer portals like Backstage were starting to sprout up in various forms, promising to make our lives easier by centralizing documentation and service information.

Kubernetes Complexity Fatigue

Yet, the reality of managing Kubernetes clusters still left me feeling a bit overwhelmed. With each passing month, the complexity seemed to grow. I found myself spending more time debugging strange container issues than I would have liked. The promise of eBPF was intriguing—promising new ways to optimize and trace performance—but it felt like there were just too many moving parts.

GitOps Maturity

ArgoCD and Flux were maturing, but the reality was that Kubernetes clusters often needed manual intervention. Setting up a robust GitOps workflow wasn’t as simple as just applying configurations from Git. A lot of time was spent arguing over how best to handle edge cases where deployments failed or caused unexpected downtime.

Remote Work Reality Check

On top of all this, remote work had its own set of challenges. Debugging issues that required local environments felt frustrating when you were on a wired internet connection, let alone when your home Wi-Fi wasn’t cooperating. The constant back-and-forth with team members and stakeholders in Slack made it hard to find real focus.

A Teenager’s Guide to Avoiding Actual Work

In the midst of all this, I stumbled upon an article that felt oddly relevant: “A teenager’s guide to avoiding actual work.” It was funny how true it felt, especially when you’re staring down a long list of TODOs and wondering if any of them were actually important. This blog post echoed what we all knew—sometimes the hardest part is just getting started.

Hosting SQLite Databases on GitHub Pages

One small victory came from hosting an SQLite database on GitHub Pages. It was a trivial task, but it felt nice to see how modern tools can solve small problems with elegance. It also highlighted how static site generators and serverless platforms were becoming more integrated into our workflows, even for simple tasks.

The SerenityOS Experiment

Then there was the story about someone quitting their job to focus on SerenityOS full-time. It reminded me of the importance of sometimes taking a step back from the norm to see if something else might fit better. Maybe the excitement of working on a new operating system, or even just focusing on personal projects for a while, could be refreshing.

Wrapping Up

Looking back at that day, it was clear that 2021 was shaping up to be an interesting year in tech. SRE roles were becoming more common, GitOps was maturing, and eBPF was gaining attention. But the core challenges of managing infrastructure remained: dealing with Kubernetes complexity, ensuring robust remote work setups, and finding ways to make our daily tasks less daunting.

As I typed up another ticket for debugging a mysterious issue, I couldn’t help but smile at how much we had already achieved—and how far we still had to go. Tech was moving fast, and so were we.