Nish Anil
I’ve always lived between two passions: building software and telling stories.
My journey into programming began long before my career did — back when I was a college kid fascinated by building computer programs using C, C++, Java, Visual Basic, and later the elegance and power of C#. Those languages didn’t just teach me how to code; they shaped how I think. They unlocked a sense of possibility that stayed with me.
That early love eventually grew into something bigger: the joy of building mobile apps for iOS and Android using .NET and C#. There was something magical about writing platform specific code in the language that I love and seeing ideas come alive across devices. It pushed me into communities, conversations, and eventually onto conference stages.
Before I became a product leader, I spent years as a Developer Evangelist for Xamarin — and those were some of the most defining years of my life.
I traveled the world meeting developers, speaking at conferences, doing live demos, swapping stories in hallways, and learning what truly matters to people who write code every day.
I traveled the world meeting developers, speaking at conferences, doing live demos, swapping stories in hallways, and learning what truly matters to people who write code every day.
I loved those interactions.
I loved the raw excitement of someone discovering a new API.
I loved the collective “aha” moment when an idea suddenly clicked.
I loved watching developers realize they could build beautiful mobile apps with the languages they love — just like I did.
I loved the raw excitement of someone discovering a new API.
I loved the collective “aha” moment when an idea suddenly clicked.
I loved watching developers realize they could build beautiful mobile apps with the languages they love — just like I did.
Those experiences taught me something fundamental:
technology is only meaningful when it empowers someone to build.
That belief guided me deeper into teaching and writing. I contributed to the .NET Architecture Guides — writing about cloud-native applications, microservices, modernization patterns, and production-ready architectural principles.
Those books began as a way to bring clarity to complex topics, but they grew into something far bigger: learning resources used by teams across the world while building real systems. It’s one of the most meaningful ways I’ve been able to give back to the developer community.
From there, I helped drive the creation of Enterprise App Patterns at Microsoft — guidance that brought together cloud-native principles, architectural best practices, and proven real-world approaches into repeatable, reliable patterns. These patterns became a bridge between what teams want to build and what actually works at enterprise scale.
Building them taught me how much clarity matters for developers navigating big, mission-critical systems.
technology is only meaningful when it empowers someone to build.
That belief guided me deeper into teaching and writing. I contributed to the .NET Architecture Guides — writing about cloud-native applications, microservices, modernization patterns, and production-ready architectural principles.
Those books began as a way to bring clarity to complex topics, but they grew into something far bigger: learning resources used by teams across the world while building real systems. It’s one of the most meaningful ways I’ve been able to give back to the developer community.
From there, I helped drive the creation of Enterprise App Patterns at Microsoft — guidance that brought together cloud-native principles, architectural best practices, and proven real-world approaches into repeatable, reliable patterns. These patterns became a bridge between what teams want to build and what actually works at enterprise scale.
Building them taught me how much clarity matters for developers navigating big, mission-critical systems.
Today, I’m a Principal Product Manager in the Core AI team, working on GitHub Copilot app modernization — helping teams transform legacy applications into modern, cloud-native systems using AI. I build tools and patterns that make hard engineering problems feel more approachable, and I work with developers to shape products that genuinely improve how they work.
But the other side of me still thrives in creativity.
I spend evenings behind a camera, experimenting with cinematography, learning color and composition, and telling stories through frames instead of functions. Photography and filmmaking give me a way to slow down, observe, and express the emotions that don’t fit in code.
I spend evenings behind a camera, experimenting with cinematography, learning color and composition, and telling stories through frames instead of functions. Photography and filmmaking give me a way to slow down, observe, and express the emotions that don’t fit in code.
Across all of this — coding, evangelizing, product building, filmmaking — there’s a single thread:
I love understanding things deeply and helping others see them clearly.
Sometimes that clarity looks like a modernization pattern.
Sometimes it’s a conference talk where everything suddenly makes sense.
Sometimes it’s a quiet photograph captured in perfect light.
Sometimes it’s a conference talk where everything suddenly makes sense.
Sometimes it’s a quiet photograph captured in perfect light.
But it’s always storytelling, in one form or another.