Two Years Running: Reflections on Being Named a Kentico Community Leader

NOTE: This image is AI Generated and definitely is not me!

When I received the notification that I had been named a Kentico Community Leader for the second consecutive year, my reaction wasn’t self-congratulation. It was reflection.

I thought about the dozens of developers I’ve traded ideas with in forums, the questions that started as quick answers and turned into deeper architectural conversations, and the partners who, over time, became genuine friends. That’s what this recognition represents to me—not a personal milestone, but the byproduct of sustained engagement in a community I care deeply about.

Being recognized in both 2025 and 2026 isn’t something I earned in isolation. It’s what happens when you consistently show up, share what you’ve learned, and invest in the people around you.

I started working with Kentico in 2013. I was initially drawn to the platform’s flexibility and its respect for developers—the sense that you could build serious, complex digital experiences without fighting the framework at every turn. What I didn’t anticipate was how central the community itself would become to my career.

Over the past twelve years, I’ve watched Kentico evolve from a traditional CMS into Xperience by Kentico, a modern, ASP.NET Core–based, headless-capable platform. I’ve seen agencies adapt, architectures mature, and development practices shift. Through all of that change, the community has been the constant.

There’s something rare about a technical ecosystem where people genuinely want each other to succeed. This recognition reinforces a belief I’ve held for a long time: technical skill matters, but engagement matters more. The real value of an ecosystem emerges when knowledge flows freely between the people building with it.

When people ask what I’m most proud of contributing to the Kentico community, it’s never a specific feature, module, or clever solution. It’s the knowledge sharing.

It’s helping someone get unstuck on a deadline. It’s the hallway conversations at events that turn into long-term collaborations. It’s being present, consistently, even when the contribution feels small.

Community leadership isn’t about having all the answers. It’s about remembering what it feels like to be stuck and choosing to respond with patience and clarity. Every experienced developer was once new to the stack. The leaders are the ones who never forget that.

One of the highlights of my past year was presenting at Partner Connections. Standing in a room full of practitioners and sharing lessons pulled directly from production reinforced why this work still excites me. Those events are where ideas collide, assumptions get challenged, and better patterns emerge.

If there’s a single theme that will define my contributions going forward, it’s AI-augmented development.

Over the past year, I’ve been working extensively with Claude Code, and it has fundamentally changed how I build Kentico solutions. Tasks that once took days now take hours. Code quality has improved as patterns and edge cases are surfaced earlier. Most importantly, I’ve reclaimed time—time that goes back into architecture, experimentation, and community involvement.

This isn’t about replacing developers. It’s about amplification. When AI handles the repetitive scaffolding, I can focus on decisions that actually matter: system design, performance tradeoffs, and long-term maintainability.

Recent launches—including a new site and the release of Lightning Enable, a Bitcoin Lightning payment integration for Kentico Commerce—are direct outcomes of this approach. Building something like Lightning Enable would traditionally have required months of focused effort. AI-augmented workflows compressed that timeline dramatically, without sacrificing rigor or quality.

That’s the kind of leverage I want more Kentico developers to experience, and I’m committed to sharing these workflows openly with the community.

If you’re wondering whether you have something to contribute, the answer is almost certainly yes.

Share what you learn, even when it feels obvious in hindsight. Attend events and talk to people outside your immediate circle. Be helpful consistently, not performatively. Communities aren’t built on grand gestures; they’re built on repeated, quiet acts of generosity.

Community leadership isn’t a destination. It’s a practice.

As I move into my second year as a recognized Community Leader, my focus is clear. I want to help the Kentico ecosystem adopt AI-augmented development responsibly and effectively. I want to keep building tools that expand what’s possible on the platform. And I want to remain present—in forums, at events, and in conversations—learning as much as I share.

The Kentico community gave me a career I genuinely enjoy and a network of people I respect. This recognition isn’t a conclusion. It’s a reminder to keep investing in the ecosystem that made all of this possible.

Here’s to another year of building, sharing, and pushing the platform—and ourselves—forward.