About¶

There is one thread running through everything I have done professionally and personally. I take complex systems, make them legible, and build communities around them. It took me a long time to see it clearly.

The magazine¶

My first senior role was editor-in-chief of a technology monthly. I got the position the honest way — I proposed the best plan and then delivered it. Running a magazine is a systems problem disguised as a creative one. Editorial calendar, contributor relationships, fact-checking pipeline, print deadlines, distribution. I was twenty-something and I loved every part of it.

What I was actually doing was documentation. Taking a chaotic inflow of technical knowledge and turning it into something a reader could trust.

The IT years¶

I moved into IT project management because that is where the work was. Twenty years of it. Complex enterprise systems, integrations, transformations, migrations. Lately a Programme Manager at Tesco CE People IT, where I became — without planning to — the documentation person. The one who built the Confluence space that actually worked.

I gave presentations on documentation practice. On AI tooling. I was the AI person before most people in the room had tried it seriously. None of this was in my job description. All of it was the same instinct I had running the magazine.

Telč¶

Five years ago my family moved to Telč. Small Renaissance town in the Czech highlands, UNESCO heritage site, population five thousand. No skatepark.

I bought ramps, protective gear and skates for kids to borrow. I started training sessions — twice a week, somewhere between movement practice, Ido Portal method, and just falling correctly. The municipality listened, trusted the project, and cooperated closely. In September 2026 a 59×19 metre skatepark opens. Bowl and street. World quality.

What I was doing was the same thing again. Taking a community that did not exist yet, building infrastructure for it, documenting its values, and letting people arrive.

libdrone¶

In 2025 I started building my first drone. Not because I needed a drone but because I needed to understand the system. A modular aerial payload platform — something anyone with a 3D printer and €250 could build and repair. EU-origin, open hardware, fully documented.

A PRUSA CoreOne built from a kit, a clear architecture, and a lot of nights. What came out the other end was a complete documentation stack — variables file as single source of truth, payload SDK, hardware specification, build guides, master specification — before the drone flew.

That is not backwards. That is how I work. Understand the system completely. Document it so a competent stranger can reproduce it without asking you a single question. Then build.

The drone is libdrone.eu.

The daughter¶

My daughter is six. She comes to skate sessions. She asks questions about the drone. She is growing up around a parent who builds things, documents things, and believes that falling down is part of learning.

I am not raising a skater or an engineer. I am trying to raise a person who is not afraid of hard things, who knows how to learn, and who understands that communities are built, not found.

Everything on this site is, in some way, about that.

What now¶

I design documentation systems. I have been doing it for twenty years without using the title.

Not writing documents — designing the systems that produce them. Information architecture, content schema, single source of truth, toolchain selection. The writing comes after the structure, and not the other way around.

I know where my competence ends. I am not an infrastructure engineer. When the pipeline breaks, that is someone else's table — and I say so before an engagement starts, not after something stops working. The right client finds that reassuring rather than limiting.

If you want to work together, the door is open.