Back to home

From taking the computer apart to building teams

The long version. From a curiosity about what was inside the box, to building software, teams, and a company around it.

At ten I took my father's computer apart. I wanted to see the thing inside the box, the part that made it work. I got it back together, mostly. The curiosity stayed.

At thirteen I had a small company building websites, which I sold in 2004. Building software for a living came later, from 2009.

That curiosity is the thread through everything since: writing software, drawing system boundaries, leading teams, teaching kids and students, giving talks, building companies, and now working out what AI means for the craft.

Where it started

I studied Business Informatics at NORDAKADEMIE as a dual student, which meant university and OTTO at the same time from 2009. OTTO rotated me through a lot of the company: controlling, SAP HR development, e-commerce, corporate strategy. I also helped get the startup incubator Liquid Labs off the ground, where Risk.Ident later spun off into its own company.

I learned something there that shaped everything after. The interesting problems are rarely only technical.

OTTO: learning to ship

In 2013 OTTO took me on as a software engineer. I joined a SCRUM team of ten building a new backoffice system for otto.de.

Then a colleague and I did something I am still proud of. We convinced leadership to start a new team focused on social media features, and I co-led it technically. Two weeks in, a small feature shipped from that team moved a single revenue line into the three-digit millions.

That taught me how much a tiny, well-placed piece of software can move, and how much of that depends on a team being allowed to build it.

Breuninger: architecture as a way to keep moving

From 2017 I was Lead Software Architect at Breuninger, responsible for the online-shop platform. Thirteen teams worked on it, 40 internal and 30 external developers.

In those years we relaunched the shop in Germany and Austria, expanded into Switzerland, and added a marketplace. Online order revenue grew 35% in 2018. We did it without piling up the kind of technical debt that quietly slows everything down later.

The lever was architecture. I established a vertical architecture that made teams customer-focused, data-driven, independent, and able to organize themselves. Breuninger is where I learned that good architecture is mostly about making change cheap.

BLUME 2000: the whole picture

As CIO at BLUME 2000 from 2020, I owned the e-commerce IT department. The team was not set up for what was coming, so we rebuilt the product, organization, and technology layers, and shipped a new online shop on a new foundation.

CIO work taught me where technology, organization, operations, and business responsibility actually meet. In small daily decisions, not in strategy slides.

TalentFormation and hackers&wizards

After BLUME 2000 I moved into company rebuilding at TalentFormation, working on architecture, delivery, and verticalization. That is where the first real shape of my agentic engineering work appeared.

Today I run hackers&wizards, the company I co-founded for agentic engineering: training, workshops, and practical AI-assisted software development. It has its own home at hackersandwizards.dev.

The teaching thread

Teaching keeps showing up. Hacker School since 2014, university lectures, mentoring, conference talks, workshops, and now working with AI systems.

The pattern is the same every time. If you want a person or a system to do good work, you have to make context visible. Examples, feedback, boundaries, patience, and enough structure that the next step becomes obvious.

That is why mentoring and agentic engineering feel like the same work to me. Getting good results out of AI is a context problem and a teaching problem before it is a tooling problem.

The question I am working on now

How do we use AI to make software teams more capable without losing craft, judgment, or ownership?

That question drives hackers&wizards, my talks, my writing, and most of the conversations I have with CTOs, developers, and educators.

If AI makes producing code cheaper, teams need stronger architecture and clearer thinking, not less of either.


The same curiosity that made me open that computer still runs the work: understand the system, make it useful, teach what you learned.

Four things that hold, job to job

Roles and companies changed plenty over twenty years. How I show up to the work did not.

  • Passionate

    Why we got into this matters as much as what comes out of it. I work to keep the craft and the spark alive in the people doing the work.

  • Relentless

    Twenty years in, I still go at the hard problem until it gives. A hurdle is the part of the climb where most people turn back.

  • Head-on

    When something is wrong, I name it early, in the room. The hard conversation now is cheaper than the one you delay.

  • Successful

    The work counts when the bar moved and the team is still the kind of place people want to be on Monday. That is the result I measure against.

Almost nothing here is original. I borrowed most of it.

The people below solved problems I keep running into, often in another decade or another field. When I am stuck between a clever solution and a clear one, I am usually borrowing one of their ideas.

Heroes

Each line is the idea I took from them, in my words.

  • Software engineering is an experimental practice.

    David Farley

    Continuous delivery

  • As independent as possible, as integrated as necessary.

    Stefan Tilkov

    Self-Contained Systems

  • Refactoring is how good software gets built, not cleanup work.

    Martin Fowler

    Software design

  • Make it work, make it right, make it fast.

    Kent Beck

    Test-driven development

  • Quality enables speed.

    Nicole Forsgren

    DORA research

  • Give control away instead of giving orders.

    L. David Marquet

    Leadership

  • Happy engineers build better products.

    Gene Kim

    DevOps

  • What happens to human purpose when machines get good at almost everything?

    Max Tegmark

    AI and society

  • Fast, automatic thinking and slow, effortful thinking.

    Daniel Kahneman

    Decision-making

  • You learn to paint mostly by doing it. Ditto for hacking.

    Paul Graham

    The hackers&wizards name

  • Every solution creates new problems.

    Liu Cixin

    Second-order effects

From the reading list

  • Hackers & PaintersPaul Graham
  • AccelerateForsgren, Humble & Kim
  • Domain-Driven DesignEric Evans
  • Modern Software EngineeringDavid Farley
  • Team TopologiesSkelton & Pais
  • Turn the Ship Around!L. David Marquet
  • Thinking in SystemsDonella Meadows
  • The Three-Body ProblemLiu Cixin

Work was never meant to be the whole frame

Most of this site is about software. This part is the rest.

  • Family

    I live in Hamburg with my family, and the rest gets arranged around that. Being a dad reset what is actually worth being stressed about. Most of it turns out not to be.

  • Staying in motion

    I think better after I have moved. Calisthenics and running are the steady part. Surfskating is the part I do because it is fun. Tennis is competitive without it mattering.

  • Games and play

    I play long-form RPGs and strategy games. A well-built one is systems design told from the inside. You notice when the designers respected your time and when they did not.

  • Still a hobbyist

    I still tinker. A functional programming idea, a domain model redrawn a few times to see if it gets cleaner. No deadline, no point beyond wanting to understand the thing.

Where this shows up

The rest of the site is the short version: the six domains, the talks, and twenty years of work, newest first.