Title: Navigating the Tech Tsunami: A November Reflection

---

November 7th, 2022. It feels like just another day on the engineering track, but looking back, it’s clear this month was chock-full of high drama and shifting tides in tech. I’m reflecting on a few key moments that resonated with me, as well as some technical battles we faced at work.

The Meta Tsunami

The headline was shocking: “Meta lays off 11,000 people.” I could hardly believe it. The news hit like a wave, reshaping the landscape of tech. It’s easy to get caught up in the excitement of the latest AI breakthroughs or the next shiny tool, but when giants like Meta start cutting, you can’t help but feel a chill down your spine. We’ve all been there—feeling that we might be next on the chopping block.

At work, we’ve been focusing heavily on scaling our infrastructure to support our growing user base. AI/ML is eating everything, and we’re no exception. ChatGPT’s success has shown us the power of large language models (LLMs), but it also highlighted the enormous compute resources required. Our team had a heated discussion about whether we should build our own LLM or stick with more established services. The financial pressure to keep costs down and efficiency high is palpable.

WebAssembly and Beyond

On the technical front, WebAssembly (Wasm) on the server side continues to gain traction. We’ve been experimenting with it in some of our microservices, and the performance benefits are undeniable. However, there’s still a long way to go before it becomes mainstream. Debugging Wasm code can be tricky, and tooling around it is still lacking compared to traditional VMs or containers.

One recent debugging session stands out. We had a mysterious issue with one of our Wasm modules that was causing an application crash. After hours of staring at the disassembled bytecode, I finally spotted the culprit: a subtle race condition in how we were handling asynchronous operations. It felt like a small win, but it took persistence and patience.

Developer Experience and FinOps

Developer experience (DevEx) is becoming a buzzword, but for good reason. Teams are realizing that keeping developers happy and productive can lead to better code quality and faster delivery cycles. We’ve been focusing on automating our CI/CD pipelines and improving our tooling, which has significantly reduced developer burnout.

FinOps, or financial operations, is another trend that’s gaining steam. As cloud costs continue to rise, teams are realizing they need to have a more granular understanding of their spend. We’re starting to implement tools like Cost Management in Azure and AWS Budgets to keep our expenses under control. The challenge is balancing cost with performance—sometimes, cheaper isn’t always better if it means sacrificing speed.

DORA Metrics and Beyond

The DevOps Research and Assessment (DORA) metrics are becoming normalized across the industry. We’ve been tracking our lead time distribution and deployment frequency, which has helped us identify areas for improvement. The goal is to move faster without compromising on quality—no easy feat when you’re dealing with complex systems.

One recent project involved reducing our deployment time by 50%. It was a mix of refactoring code, optimizing infrastructure, and streamlining the deployment process. It wasn’t glamorous, but it felt good to see those metrics improve.

Accidental Google Pixel Lock Screen Bypass

The accidental bypass of the Google Pixel lock screen is another reminder that security can be fragile. This kind of incident highlights the importance of thorough testing and continuous integration in security practices. While I’m not involved with our mobile apps directly, it’s something we keep in mind when designing our APIs and backend services.

Wrapping Up

Reflecting on November 2022, it feels like a whirlwind. The tech industry is constantly evolving, and staying on top of new trends while maintaining stability can be a challenge. We’re all just trying to navigate the storm and keep our heads above water. As always, there’s more work ahead, but I’m excited about what lies ahead.

Until next time,

Brandon