Johannes Koch

Prepping my re:Invent Code Talk and remembering why live coding can be terrifying: no slides to hide a broken build behind or a failed deployment. 60 minutes, onboard a service through a platform, live. If it breaks, everyone watches it break. Worth it though. Nothing proves a golden path like running it in front of people.

How much of your pipeline is designed, and how much just accreted one urgent fix at a time?

Does your onboarding ask developers what they need, or what you assumed they need?

re:Invent is COM323, Wednesday Dec 2, 13:30, Caesars Forum Forum 120. 60 minutes, four live demos, zero slides memorized. Come dare the demo gods with me. #reInvent

A platform without an owner isn't a platform. It's a haunted house with good intentions.

If the model is a commodity now, is your edge the tools around it, or the taste to know what's worth building?

Round two at CLC: Our session is starting now. If you've ever argued self-host vs API for LLMs, come watch us compare the right units for once. Real numbers, no vendor marketing.

CLC day two. Round two with Tobias Kässer: LLM FinOps and the cost comparison everyone gets wrong.12:15 CET. Bring your "self-host vs API" argument, we'll give you the right units for it. #CLC_Conf

The LLM cost mistake Christopher and I take apart at CLC: putting a per-token API price next to a per-hour GPU price and calling it a decision. Different units. Normalize to cost per million tokens at your real traffic shape and the answer often flips.

I keep landing on "the right default and an honest number" over endless options. Where in your stack did more configurability make things worse, not better?

Train with Joe exists because generic vocabulary apps bored my kids. Loading this week's actual school words was the whole unlock. Smallest possible feature, biggest possible difference to the one user who matters.

Is infrastructure-as-code repeatable in practice, or just repeatable until someone clicks in the console once?

Backstage is great at the one-shot creative act: make a repo, scaffold code, wire a pipeline, once. Crossplane is great at the continuous reconciling act: keep the deployment matching the declared Service, forever. The demo is about not forcing one tool to do both.

CNOE idpbuilder gives you Argo CD + Gitea + Backstage on a kind cluster in one install. The platform team's job starts on top of that: the Service XRD, the Composition, the downstream namespaces. Know what's batteries-included vs what you own.

You don't have a golden path if nobody can tell you, out loud, what's off it.

On safari with Miriam at #CLC_Conf Team topologies in the wild - interesting stories and a fun way of presenting them 🫶 #TeamTopologies

I need to get @darkosubotica and @stack72 on the same stage. Life goal. #CLC_Conf

Is your golden path the fastest route, or just the only one you blessed and everyone resents?

CLC Conf is kicking off with the keynote by Paul Stack I was really looking forward to this one and to meet Paul in person 👨‍💻 Great content: Why SREs and AI agents are a perfect match #CLC_Conf

CLC day one. On stage with Sönke Sothmann today: CRDs as a platform API, the two-stage Crossplane pattern. 16:30 CET in Gustav Mahler 2. Come find me after, the hallway is where the real conversations happen. #CLC_Conf

CLC day 1 is in full swing. Kubernetes Custom Resources as Your Platform API: Declarative Self-Service with Crossplane. 16:30 CET in Gustav Mahler 2 If you care about platform teams offering self-service without exposing all the plumbing, this is the one. Declare intent, commit, deploy. See you there. #CLC_Conf