Consultancy & architecture
Clear architecture choices for .NET and Azure landscapes that grow with your organisation.
Software
creations
that connect.
Software architecture, consultancy and custom development. Carefully designed, built test-first, amplified by AI, ready for change.
Expertise
Most of my projects have a significant integration component: years of experience with distributed systems, message-based communication and service bus architectures.
Architecture that is built for change. Message based and vertical slice architecture where they fit, but always as simple as the problem allows.
AI is part of how I build software every day, with automated checks to keep it in line. I also help teams find a way of working with AI that fits their process.
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
Broad Azure knowledge for integration architecture, design and development: Container Apps, API Management, Pipelines and infrastructure as code.
One of my core tools for reliable, message based communication, with many years of experience across multiple production projects.
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
What I do
[01] servicesCustom development
Applications, APIs and portals that are thought through and fit exactly how you work.
Integration & messaging
Connecting systems reliably, with NServiceBus and event-driven architecture where they fit.
Test-driven development
Tests first, as a living specification. Code you dare to let AI change.
[02] vision
Hands on.
Hands on.
Always learning.
Every project teaches me something new, and I want the next one to be better for it. I still learn every day, and I intend to keep it that way.
Good architecture means thinking in both the big picture and the detail. And code is the most precise design notation there is. So sound architecture decisions and honest advice only come from staying close to it. That's why I keep building myself.
In this age of AI I may no longer type every line, but I keep experimenting, adjusting and improving: trying new tools, keeping what works, dropping what doesn't.
It's all in the details.
[03] AI as amplifier
Amplified by AI.
Amplified by AI.
Always in control.
I use AI to move faster and explore more options, not to hand over the wheel. Automated checks guard my standards on every change, so we can trust it is done right.
In control
AI suggests, I decide. Architecture and design choices stay deliberate and explainable.
Maintainable
Readable code with clear names and small parts, so you can keep building on it, with or without AI.
High quality
Tests first, for generated code too, and automated code quality checks on every change. The safety net that keeps speed from turning into debt.
Your team too
Want to bring AI into your own development process? I advise on where it helps, where it doesn't, and which checks keep the quality up.
Approach
[04] from idea to production
-
[01] Explore
Sharpen the problem together: what should it do, for whom, and what is good enough? You rarely know everything at the start, and that's fine. We sharpen it as we go.
-
[02] Build
Test-first, in short iterations. Better to find out early what's wrong, so we can get it right. Working software every week instead of status reports.
-
[03] Embed or support
Documentation and handover, so your team can carry on independently. Or I stay on: support backed by an SLA, so you don't have to worry about it.
[05] the logo mark
Connecting the dots.
The dots stand for connecting business and technology, and connecting systems. In the right way, avoiding complexity where possible.
The unconventional square? That's thinking outside the box, to come up with the best solution for your business.
[06] about
“Keep it simple. Think it through.”
More than two decades in software: first at various software companies, now with Byte Nine. What stands out most: keep it simple. Software gets complex fast enough on its own, so simplicity is essential. That's why I think every scenario through before a single line of code is written. How do we test it? What will change?
Teun Berkers — founder of Byte Nine
Let's
connect.
