CLOUDY MUSINGS

One of the more interesting things about enterprise AI adoption is how quickly people become comfortable with these tools. We spent years teaching users to be skeptical of links, cautious with downloads, thoughtful about where sensitive data goes, and generally a little suspicious of shiny new software. Then AI assistants showed up, proved useful in about thirty seconds, and a lot of that caution went straight out the window. Suddenly people are pasting customer contracts in

I have watched some version of this play out enough times now that it almost feels like a rite of passage for organizations trying to mature their engineering operations. The symptoms are usually familiar. Incidents are happening too often, engineers are burned out, on-call has become something people dread, leadership wants fewer escalations, and somewhere in the middle of all that, someone says, “We need an SRE.” From there, a requisition gets approved, somebody smart gets

At some point you look across your repos and realize you've got some sort of split personality problem. Half your projects are on main, the other half are still on master, and every time you touch a pipeline, clone a repo, or write documentation, you have to stop and remember which one you're dealing with. You know it's not broken, it's just inconsistent enough to be a persistent low-grade annoyance. I recently went through this myself and thought about adding this to my blog

Note, this issue affected me recently, so I wanted to blog about it and hopefully help folks out in the future. You know the pattern: You've restarted Teams. You've cleared the cache. You've uninstalled and reinstalled. Twice. Maybe three times (I know I personally lost count). And yet every person in your meeting is a gray silhouette, except for whoever happens to have their camera on. This is a specific, reproducible pain on Mac with New Teams, and the reason the usual fixe

As with previous posts, all source code and a corresponding GitHub repository can be found here! This is one of those questions that seems like it should have a straightforward answer, but it doesn't because what good fun would that be if there were a straightforward answer? I'm sure you've been here before: someone spots an enterprise application in Microsoft Entra ID, notices it has permissions or credentials attached, and naturally asks: who created this thing? If you star

Cloud conversations still tend to start in the same place. We talk about scalability, resilience, performance, and maybe security if we are feeling disciplined. Cost usually shows up later (way later), almost like a postscript to the architecture. It is something we validate after the system is live, after usage patterns are real, and after the bill gives us a reason to care. The problem with that sequence is that by the time cost shows up, most of the meaningful decisions ha