Who is behind this blog?

The People Behind Daily DevOps & .NET

Daily DevOps & .NET is written by people who believe that great systems (of all kinds) emerge from balancing seemingly opposing forces: innovation and stability, progress and professionalism, experimentation and reliability.

What We Care About

We share a passion for moving forward while maintaining quality. Our content reflects these core interests: embracing innovation with stability—trying new possibilities without sacrificing reliability. We believe in progress with professionalism, advancing continuously while maintaining high standards. We approach experimentation with responsibility, trying new approaches with full awareness of consequences. We combine curiosity with skepticism, staying open to new ideas while questioning the hype. And we pursue growth with sustainability, improving systems without creating unsustainable complexity.

Our Shared Journey

Over years of building systems—from small tools to enterprise-scale platforms, from greenfield projects to legacy modernization—we’ve accumulated experiences that shaped how we think about our craft. We’ve seen technologies come and go, watched trends rise and fall, and observed what actually survives in production over time.

What started as learning individual tools and techniques evolved into understanding broader patterns. We began to recognize that the most important questions aren’t about which framework, language, or methodology to use. The real challenges lie elsewhere, in the tensions that every team faces but rarely talks about explicitly.

We’ve learned to ask ourselves different questions now. How do we evaluate new opportunities without getting caught up in chasing every trend that promises to revolutionize everything? How do we improve our systems continuously without destabilizing the foundation that people depend on? How do we stay innovative and forward-thinking while simultaneously being reliable partners to our teams and organizations? How do we balance the pressure to move fast with the responsibility to build things that will last beyond the next quarter? And perhaps most importantly, how do we maintain professional standards and quality in a field that changes faster than any individual can keep up with?

These aren’t abstract theoretical questions. They’re the daily reality of working with real systems, real teams, and real constraints. We’ve made mistakes, learned from them, and watched others navigate the same challenges. We’ve seen what works in practice, what fails despite looking good on paper, and what depends entirely on context that nobody mentions in conference talks.

This journey taught us that there are no universal answers—only thoughtful approaches to recurring tensions. These questions guide our thinking, inform our decisions, and shape what we write about. They’re the lens through which we evaluate new technologies, practices, and ideas.

What Makes Our Perspective Different

We’re not selling solutions or promoting specific approaches. We’re exploring the tension between innovation and stability—because that’s where the interesting decisions happen. We believe that progress comes from thoughtful evaluation, not from blindly following the latest trend or rigidly clinging to the past.

Whether you’re navigating change in your organization, evaluating new opportunities, or trying to maintain quality while moving forward, you’ll find perspectives here that acknowledge the complexity of these decisions.

Want to know more? Check out the individual profiles below.


Jendrik Brack

Jendrik Brack

DevOps engineer with a systems-administration background; focus on Azure, CI/CD, IaC and pragmatic automation solutions.
Martin Stühmer

Martin Stühmer

Martin is a software architect and developer who has spent nearly two decades navigating the .NET ecosystem from Framework 2.0 to modern .NET 10. As Director Consulting Services at CGI and a Microsoft Certified Trainer, he specializes in cloud-native solutions, enterprise architecture, and Risk and Cost Driven Architecture (RCDA). His mission is straightforward - help teams build quality software that survives contact with production. He contributes to open-source communities through NuGet packages, writes about pragmatic software engineering on this blog, and trains developers who want substance over buzzwords.