Central product system
Designed and built the system at the heart of SoftwareONE's software delivery process, replacing manual steps with one digital flow.
System ArchitectThe work no one sees, so everything else just works.
I've spent almost 20 years at SoftwareONE, growing from full-stack developer to system architect. Along the way I've learned to look for the big picture and to build trust, so people tell me what's really going on, even when it's uncomfortable. I aim for software that is good enough for what it needs to do, and no more complicated than that.
Where technology meets business, I build the bridge.
Business talks about goals, customers and deadlines. Engineering talks about services, data and failure modes. I learn both languages until I can explain each side to the other.
Good architecture is translation. I turn business goals into clear boundaries and explicit data flows, and I hold the system to one consistent set of ideas. That's conceptual integrity. Written-down decisions make it visible, so everyone can see why the system looks the way it does.
A bridge only works when traffic flows both ways. Requirements come in, working software goes out, and feedback finds its way back.
Good architecture starts with the business problem, not the technology. I look at the whole system, question assumptions, and keep the people who build and use it in mind.
I talk to people openly, listen closely, and try to understand where they're coming from. I explain difficult situations honestly and help out where I can. Over time, people come to me with the real story, including the problems they wouldn't raise anywhere else. That's how hidden risks surface early and teams fix them together.
A change in one service ripples through teams, data and operations. I look at the whole picture before I optimize a part.
I question ideas directly, including my own, and I listen to the people affected by a decision before I make it.
Technology is a means. Every design should make a real process faster, cheaper or more reliable for the people using it.
The simplest system that solves the problem is the easiest to run, change and hand over. That is what keeps customers satisfied.
Macro architecture today, micro architecture from ten years of hands-on development.
Production C# since the .NET Framework days, now on modern .NET.
Provisioning, deploying and securing Azure services as code.
Secret-free service-to-service access and solid authentication flows.
Automated tests first, and visibility once it runs.
Agile in national and international teams, in client projects and in-house products.
UI work from my full-stack years. I can still build it, but it has rarely been my focus in the last five years.
Architecture and implementation of a central product system that digitizes SoftwareONE's software delivery process.
Architects from different teams solving cross-team problems: a shared library for automatic access-token renewal, plus guides on Managed Identity, Key Vault and zone-redundant Azure services.
Front-office automation for quotes connected to the ERP, a product and price system with automated price-list imports, and a purchase price API for inside sales and customers. Onboarded new colleagues to Azure and infrastructure as code.
UI lead for the COMPAREX Online license procurement portal, a Microsoft CSP subscription portal and an early microservice proof of concept on Azure. Client projects for Swiss retailers (VB6 to .NET migration), Saxony's population register (SAKD), the German Environment Agency and a video portal on Azure Media Services for Deutsche Wohnen.
Taught teenagers JavaScript, HTML and p5.js by building a small jump-and-run game together, in an initiative of COMPAREX and the City of Leipzig.
AZ-900Microsoft Azure Fundamentals70-533Implementing Microsoft Azure SolutionsMCSAWeb Applications70-486Developing ASP.NET MVC Web Applications70-480Programming in HTML5 with JavaScript and CSS370-516Data Access with .NET Framework 4Designed and built the system at the heart of SoftwareONE's software delivery process, replacing manual steps with one digital flow.
A central product and price catalog that imports price lists from many sources automatically, monitored end to end.
In the Architecture Chapter: a token-renewal library used across teams and guides that made Managed Identity and Key Vault the default.
Racing EA Sports F1 in the MRL Sim Racing league. Consistency and race craft matter more than one fast lap, much like running production systems.
Time away from the screen is where many designs get clearer.
A team sport where nobody wins alone, and training that rewards showing up regularly.
Building something with my hands, with real materials and no undo button.
Places I've been and what I took away from them, written up on my travel blog.
Talks at our internal Developer Open Space, many internal wiki guides, and mentoring at TechTeens Leipzig.