Skip to content

Profile

Software architect & engineer in Berlin. This page describes how I work, what I am building right now and what you can book me for as a trainer and architect.

I come from development, and as an architect I like to work where several systems, teams and interfaces meet. What appeals to me is not the biggest architecture but the simplest one that still carries the problem. Today I build my own products and support teams with architecture work, coaching and workshops.

Software30+years of experience
Digital products15+years with distributed systems and APIs
Passing it onsince 2014workshops and training

From the business problem to the product#

Architecture and technical depth remain my craft. But I start earlier, with the business domain: what should the product do for whom, and which first step can be delivered and operated?

Product in small steps

I develop product and architecture together with the team, in small steps that can each be shipped. After every step there is feedback before we plan the next one. A big target design at the start matters less to me than a system that can grow along the way.

Business domain and DDD

It starts with the language of the domain experts, with their terms, rules and responsibilities. With Domain-Driven Design I turn that into models, APIs and events in which you find these rules again in the code.

Organizing knowledge

I organize sources, statements and their versions so that you can look up where a statement comes from and whether it still holds. People need that in documentation just as much as agents that work with a company's knowledge.

Presenting and explaining

Before I build a page, a report or a diagram, I clarify which question it is meant to answer. Then I put statements and evidence into an order you can follow. Only after that do I choose the form.

How I think and build#

Good systems rarely emerge on the drawing board. I work my way toward them in short loops, write tests before I am sure, and throw code away as soon as I have understood something better. Over the years I have seen many technologies come and go. The systems that lasted longer were the ones with clear boundaries and good names.

I am at home in event-driven architectures with CQRS, Event Sourcing and Domain-Driven Design, mostly with Node.js and TypeScript, GraphQL and React or SvelteKit on AWS. What matters to me is that the business intent stays visible in the code, through clear domain boundaries and expressive types.

Agentic Engineering#

Since late 2025 I have been working with coding agents every day. Agentic coding means that an agent reads, changes and tests code. Agentic engineering is the system around it: it makes sure that the results also hold up in production. Generating becomes cheap, verifying becomes the bottleneck, and that is exactly where I start.

Harness and context

Tools, context and executable checks turn a task into a reviewable branch. The model is rarely the bottleneck here, the harness makes the difference.

Rules that apply

Instruction files remain recommendations. What has to be binding I enforce in the path: with a check before the effect, approval and evidence.

Grounding and knowledge

Answers rest on real sources or say that nothing is there. What a team learns along the way, it maintains like code: with origin, versions and owners.

Agents and interfaces

I cut agents along the business domain and connect them via MCP, HTTP, webhooks and A2A.

None of this is an AI invention. Domain-Driven Design, approvals, versioning and audit have held up for decades; the only new part is that a model acts in the loop. How I got there is described in the series From Session to System. You will find all articles under the topic AI.

What I am working on right now#

What counts is not that a model produces an answer. What counts is whether its origin stays visible and a person can check it. That is what I work on in SubKit: one person builds a workflow with the help of the AI, reviews it and approves it. If colleagues want it too, they start it with their own permissions, and every run stays on record.

Alongside that I am building two apps. Harmoniqs is an app for songwriting on Mac, iPhone and iPad. TackTics is a sailing trainer and still in progress: the app is meant to combine NMEA data, weather and past trips so that trim and maneuvers can be analyzed step by step. More on the projects page.

What you can measure me by#

Open source, in real use#

My adapter sveltekit-adapter-aws brings SvelteKit serverless to AWS – others now run it in production.

Writing since 2014#

In the blog I write about the craft, from katas through GraphQL and reactive architectures to delivery, teamwork and product thinking. Since late 2025 AI has joined the list. Explaining forces clarity; that sharpens your own code too.

Passing it on#

Since 2014 I have been training teams in architecture, GraphQL, Node.js and Domain-Driven Design, preferably on their own tasks. Today this is available as workshops, online, remote or on-site. The hands-on introductions to GraphQL, Node.js, React and other topics are freely available.

Away from the screen#

When I am not sitting at the code, I am drawn to the Alps, on the road bike, on the rock face or on a ski tour. Music is just as much a part of it: guitar and piano. And in summer I like nothing better than sailing my Seascape 24 SE on the Havel and the Wannsee.

Contact#

Write to me if you want to discuss an architecture topic or request a workshop for your team: mike.bild@gmail.com. I am based in Berlin.

Publications and talks#

Technical articles and talks since 2010, from coding dojos to serverless, are collected under Publications and talks.