40 Years of Code, 200 Repos, and the Search for the Right Team

Update April 2026: This post is from January 2026. Back then I was looking for "co-founders" — today the direction is clearer: the workshop is running, AI tools like Conductor are live, and in parallel I'm building SME analytics as a cashflow arm. Collaborators, sparring partners, and Innovation Circle folks are still very welcome — the formal co-founder track is closed.

The Elephant in the Room

I'm turning 60 this year. In my generation, that usually means: planning for retirement, learning to play golf, maybe writing a book about "the good old days of software development."

I have other plans.

After 40 years in the industry — IBM, PwC, countless projects from mainframes to mobile apps — I've come to a realization I can't shake: The most exciting things don't happen in corporations. They happen in small teams that build fast and learn even faster.

And that's exactly what I want to do again. Not as a consultant producing PowerPoints. As a builder who writes code.

Why This Blog Exists

I have over 200 repositories on GitHub. Some of them are toys, sure. But many are real projects — ideas I started at 10 PM because they wouldn't leave me alone.

The problem: Most of them, nobody knows about.

This blog is my attempt to change that. I'll be building in public here. Every project, every idea, every failure. Transparent and honest.

What I'm Looking For (And What I'm Not)

Let me be direct: I'm not looking for clients.

I've been consulting for 20 years. I know how the game works — negotiating day rates, acquiring projects, writing invoices. It works, but it doesn't make me happy anymore.

Back then I was looking for co-founders — people who wanted to build something together with me. Today the formal co-founder track is closed; what remains are collaborators, sparring partners, and Innovation Circle folks. Not for an exit in five years, but because the work itself is fun.

My contribution: 40 years of technical experience, the ability to build prototypes in days instead of months, and a pile of ideas just waiting to be implemented.

Your contribution: No idea. Maybe design. Maybe sales. Maybe just a different perspective and the willingness to try things out.

The Philosophy Behind It

I ship instead of advise.

That's my mantra. After decades in consulting, I know: Most strategy papers end up in drawers. Most concepts never get implemented. Most meetings could have been emails.

What counts is working code. A prototype you can touch. An MVP that has real users.

That's why you won't find abstract frameworks or buzzword bingo here. Instead:

• Real projects — with code, screenshots, and honest assessments of what works and what doesn't
• Technical deep dives — when I learn something interesting, I'll share it here
• The unvarnished truth — including failures, because that's where you learn the most

The Projects to Come

A small preview of what I'm currently working on:

Agent-Flutter — Why are there no AI agents for Flutter? I'm building one.

GitKeeper — A tool that analyzes my 200 repos and tells me which ones I should revive.

Open NoiseNet — Citizen science for noise pollution. IoT sensors for everyone.

And several more. Some will work, some will fail. Both are part of the journey.

The Deal

I promise to write here regularly. Honest, direct, without marketing speak.

If that interests you — follow me on Twitter or Bluesky. Or write to me directly if you'd like to build something together.

I'm curious where this leads.

Uli, February 2026