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.
EKS Auto Mode plus managed Argo CD, ACK and kro already took most of the node babysitting away. What I want next: managed Crossplane, easier networking defaults, and faster cluster provisioning so ephemeral clusters are actually practical. The data plane got solved. The control-plane experience is where the next wins are.
Heading to Mannheim for CLC 2026. If you're there, say hi. Two topics I care about, one theme that keeps recurring across both: people don't want more options, they want the right default and an honest number.
The money moment in my COM323 demo: change one field, tier standard to critical, and paging flips to 24x7, scan cadence goes daily to hourly, the SLO re-derives. One field, owned by the platform team, in one place.
Mannheim this week for CLC 2026. Two talks: platform APIs with Crossplane, and LLM cost reality.
If you're attending, the hallway is where I do my best thinking. Come find me.
#CLC_Conf
Reversibility is a feature. In the demo, deleting one Service CR cascade-cleans the deploy, three registrations, the repo and the GitOps record. If a delete leaves ghosts, you built a liability, not a platform.
My re:Invent demo bets the memorable moment is one tier change rippling across six systems. What's a demo moment that made you want the thing on the spot?
Writing blogs in 2026: AI made the first draft free, which means the only scarce thing left is having something true to say. The draft was never the valuable part.
AWS Community Builders isn't a reward for expertise. It's a program for people who consistently share, at any level: blogs, demos, talks, open source. Build in public first, then apply in the next cohort.
Use a CRD as your platform's API and you get declarative state, reconciliation, RBAC, audit logging and GitOps for free. That's the CLC talk with Sönke in one sentence.
I claim onboarding should be three fields: name, team, tier. How many fields does your real onboarding form have, and how many does anyone actually understand?
I think the agent should onboard a service exactly like a human: same Service CR, same guardrails. What's the one thing in your platform you'd never let an agent apply unreviewed?
Build-in-public honesty: I ship more side projects than is sensible because each is a different stress test of how far agentic coding gets me on something real with real users.
We test Crossplane compositions like application code, before a developer's first onboarding. Composition patches fail opaquely and the feedback loop is slow; the test suite is what turned a three-month composition into a boring one.