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

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

Why You Should License Your GitHub Repository When you publish code on GitHub without a license, you automatically retain full copyright. That means others can read your code, but they cannot legally copy it, modify it, or redistribute it. In short: Public does not automatically mean open source. No license means no permission for reuse. GitHub is explicit about this. For a repository to be considered open source, it must include a license that grants others the right to use,

All code for this blog can be found here . I keep hearing more and more interest by customers I work with in exploring Cloud...

All code for this blog can be found here . I've been trailblazing with Azure since 2016. Before 2016, I set up an Entra ID (formerly...

I know in my last post; I mentioned I would take you through real life examples of using public APIs using Postman. It dawned upon me as...