Twilight Imperium
Just One
Tiny Epic Galaxies
Recall
Gizmos
Humanity
Tempel des Schreckens
Aquatica
Root
So you’ve been eaten

Localized results tho.
You did give me the idea to create an accompanying bekug website. Cheers!

What immediately comes to mind is seeing a test fail and not understanding from the failure message why it’s failing. E.g. toString() wasn’t implemented and now all I’m getting is reference id’s that are different when I expected to see the properties of a value object being different.

1/ Experiments are useful to learn what's possible, to discover your blind spots, to generate optionality (aka the availability of options even when you don't need them), and to allow innovation. Without experimentation for the sake of discovery, there's no science, art, philosophy.

I was wondering the same thing. When you know it’s a human that wrote it, there’s empathy: “whoever wrote this was under lots of constraints at the time and I’ve been there myself once. I’m happy to fix this code that does something valuable”.
But I can’t apply that when it was vibe coded.

Cheeky :)

What is keeping _your_ teams from using Kotlin? Wrong answers only.

Hmm. There’s also Promising Young Woman, Saltburn, or Jennifer’s Body.

We watched Barbarian the other day and I can recommend it. Horror yes, sci-fi no.

Thanks for sharing. That’s also my experience. We’ve been doing that for 4 years in my current team of 8 and organize ourselves in pairs to “swarm” on a feature. We first mob to define contracts. Sometimes there still are conflicts but they’re only really bad when we didn’t communicate well enough

Curious to learn what your experience with it was like. Is it different from how you’re working today?

I’m not saying it’ll fix your merge conflicts, but trunkbaseddevelopment.com is a thing that you might want to try at some point.

😭

This ended up being a massive spoiler for me but I still laughed my ass off seeing it.