As I’m flying from Oslo to Amsterdam, I’m still buzzing with energy and inspiration from NDC Oslo 2025. It was an incredible week of learning, sharing, and connecting with some of the brightest minds in technology. From thought-provoking keynotes that challenged our assumptions to the epic The Linebreakers concert at Brewgata, every moment reinforced why each NDC conference but NDC Oslo remains one of the premier developer conferences in the world.
I’m excited to preview my upcoming NDC Oslo talk, “Resilient by Design”, where I’ll share how to architect Azure systems that not only survive failure but continue running smoothly when disruptions occur (NDC). Join me on to explore core resilience principles, Azure-native tools, and proven best practices for maintaining high availability in real-world scenarios (Microsoft Azure, Microsoft Learn). Whether you’re new to Azure or looking to optimize an existing environment, this session will equip you with actionable strategies to anticipate, mitigate, and recover from failures (Microsoft Learn).
I’m thrilled to announce that I’ll be delivering two sessions at Techorama Belgium 2025! Join me as we explore the cutting edge of .NET, AI, and cloud resilience with actionable strategies, demos, and real-world insights. Techorama Belgium is a premier tech conference that brings together developers, architects, and IT professionals to share knowledge and network with industry leaders. This year, I’m excited to be part of the lineup!
This month at Stir Trek 2025, I presented on Dev Containers and GitHub Codespaces, demonstrating how these tools streamline both local and cloud-based development workflows. The session covered the essentials of creating portable development environments, customizing containers with features and extensions, and launching Codespaces directly from your repository. A lively Q&A followed, with attendees asking about strategies for running and working with multiple containers. Below, I’ve distilled those discussions and provided a deeper dive into shared container configurations across multiple projects-including folder structures, Docker Compose setups, VS Code workflows, and advanced tips you can apply in your own work.
Rubber Duck Debugging in the Age of AI # Ever found yourself explaining your code to a little rubber duck perched on your desk? If so, you’re in good company. This quirky practice, known as rubber duck debugging, has helped countless developers articulate problems and discover solutions. The idea is simple: by forcing yourself to explain your code, line by line, to an inanimate duck, you often stumble upon the bug or insight you needed. It’s like having a silent pair programmer who patiently listens as you work through the logic. But what if your rubber duck could talk back and offer suggestions? Modern AI coding assistants (like GitHub Copilot) are becoming the new interactive rubber ducks, and that means a lot for debugging, brainstorming ideas, and reviewing code.
I wanted to share a quick work update and also explain why I’ve been posting less frequently lately. Previously, I was on the Fast Track for Azure (FTA) team at Microsoft, part of the Customer Experience Program (CXP) within Azure Engineering (C+AI). In October, my team was reorganized and I was moved into the Azure Reliability (AzRel) group.
I’m now part of the AzRel Risk SRE team, focusing specifically on risks related to Azure Platform Reliability. My new role brings with it a significantly different skill set and area of focus, requiring a deep dive into new concepts, tools, and approaches. I’ve been fully engaged in learning and adapting, and I’ve also been actively developing new applications and solutions to address challenges faced by my new team.
