Hire people who removed code (not tests). Don't look for people who added the most.

Lang ist es her, und es ist wieder Zeit: unser Kubernetes Meetup in Frankfurt in Neuauflage: Modern K8s. Am 3. November im @codecentric Office. https://www.meetup.com/frankfurt-am-main-kubernetes-meetup/events/311516952/

Tell me you're old without telling me you're old.

kc – kubernetes commander

Don't trust code that you have not vibe coded yourself.

When working with an agent, will you put requirements and stories into Jira?

Graphical user interfaces were a detour. vt100 is all you need #llms

Today is a good day to vibe code something. Wish me luck.

Is it time for comment-free code? And then an IDE adding them dynamically following your favorite style on-the-fly?

Every time again, car rental must be disrupted. Looking at you @TeamEuropcar_en. If you want to experience (IT) processes of the 80ies, this is the place.

"Did I leave the agent coding in yolo mode?" is the new "Did I switch the stove off?"

Wow, @twintapp in 🇨🇭 is so incredibly 2002. Prepaid payment where prepaid means to put money on your mobile by buying credit at @coop_ch shops, at least for us non-Swiss visitors without Swiss bank account. Telefonkarten Vibes.

Added custom subresources to CRDs in our internal kube code based generic control plane: 194 lines of code. One day of work 😎

Little @KubeCon_ fomo. Have a great conference everybody!

multicluster-runtime provider that watches kubeconfig secrets in a namespace and dynamically engages controllers 🚀 https://github.com/kubernetes-sigs/multicluster-runtime/pull/45

AI creates PR (on my machine). I review. Can I approve? What does the Github/lab netiquette say?

After a little operational hickup where the app got deleted and GitOps eventually recreated everything, OH: "I only wish that the db would have been also deleted to test backups"

This costed me a day and a half: When watching via Golang types in controller-runtime, but use unstructured when reading from the cache, you are in trouble. Of course, 2 informers are run and they are not consistent aka events arrive and you don't see the changes in the cache.

Linter.

Try to build a bridge from A to B over a deep valley. No car will be able to pass before a certain point. Not even a bicycle or human can. The measure of progress is not the thing that can pass. The measure is not continuous. There is a point when everything comes together.

There are tasks that are not iterative. Tasks that take days or weeks or more of super focused time until you see success. I call them Heavy Liftings. Making them iterative with sensible intermediate steps makes them infeasible or way slower.

We need fewer lists, more visual representations in work communication. Will AI help?

SQL, columnar, NO SQL, graph, and vector databases

The real planning tool is gdocs. Jira is an asynchronous replica. Mostly out of date. Never consistent.

Jira must be disrupted. Please.

Strong opinions, loosely held. Still a thing.

„directly share“ in @LinkedIn irritates me every single time. It‘s a dishonest term. It really means „shared with network“ and NOT directly with you. Pure clickbait.

Talking about critical path. MVP is the spiritual successor in a less plannable environment. Visibility of necessary focus is what they have in common.

Why has „critical path analysis“ disappeared from the usual toolset of project mgmt (at least in IT, cloud native system and software development) ? Am always amazed that nobody talks about it. No engineer is aware of being on the critical path.

Where does it differ from previous kube-in-docker approaches in the last 10 years, most prominently implemented in kind today.

@fabiankramm please correct where I am wrong. If I was building that, not sure I would run a full kubelet, or in general kubelet expecting full node ownership would be my first concern. Am curious which route you took.

Product explanation as a service. Today @loft's vNode: Run multiple containerized kubelets in pods side-by-side, use Linux cgroups and namespace constructs for isolation and expose these to vclusters.

Digital software gardening producing goods for the bazaar not the cathedral.

Serious question, is Jira of today exactly the same as in 2013 ? GreenHopper at the time. I had hope.

Where is your distributed bottleneck? 5/5

Conflict free data structures by design are magic, but applying them can be counter intuitive. Designing for distributed scale can look trivial. The local rules often are. But finding the right local rules is a science. 4/5

Astonishing how we are distributed system experts, but fail to apply the basics to our distributed teams. Global locks are bad. Lock contention is real and can break throughput. Local decisions are preferred. Global consensus is expensive. Shared mutable state slows down. 1/5

We exactly want abstractions like APIs because not everybody should have to know everything of a complicated system. And if that works out, it's not a failure but success.

„It shouldn‘t be a kube-like API because ppl expect REST“ is a requirement I have heard again and again for years. What does it mean?

Abu's and my @KubeCon_ talk about the Life (and Death) of an API Request in kube-apiserver is up! Enjoy! https://www.youtube.com/watch?v=Hc0jj-654lA

Our @KubeCon_ talk about https://github.com/kubernetes-sigs/multicluster-runtime is up. Enjoy! https://www.youtube.com/watch?v=Tz8IcMSY7jw

Have just ordered slim wallet compatible with German Fahrzeugschein from Japan. How is your weekend going?

You cannot name, you don‘t understand.

220, 7, 1

Unpopular opinion: GPT 4o just sucks in capturing the face proportions of real people. Every caricature artist in the touristic quarter of your favorite travel destination is a lot better. And this @Apple Playground app is even worse than GPT.

That moment when sitting in front of a German keyboard and the shortcut is CMD-[ 🥴

Stock market is crashing and people are turning every photo into a 3d cartoon character as distraction.

best kubecon ever, london was. thank you everyone who came to see my talk.

Heard some negative sentiment about this KubeCon. For me seeing all old friends and connecting to new ones made it one of best KubeCons I can remember. As usual, the hallway track makes the difference, not the talks or sponsors. Thank you everybody for making it a blast.

Little @KubeCon_ talk promo. Join Abu and me talking about The Life (or Death) of a Kubernetes API Request, 2025 Edition. Long ago Daniel Smith gave a talk with the same title. But a lot has changed since then, and a new generation of users arrived https://sched.co/1tx89