Thomas Dohmke

And we see this in AI even faster than we've ever seen it before.

And so it means no matter what project you're looking at, you've got to see, okay, so what are they doing next and how often can they keep up with the work?

And that is as true in the enterprise or in the commercial software space where you keep your source code close than it is in the open source space.

And the best way I can describe this is like they're all playing Minecraft.

There is no ultimate win.

There's little mini wins that you have, but you're playing an infinite game.

You're playing an infinite game and

survival, survival and staying, you know, staying on top of it, that is actually the, that is actually the skill for software engineers and the groups, you know, that they're forming to build companies.

The magical thing, I think, for every LEGO enthusiast is that I can give it all my unsorted LEGOs and it perfectly sorts them by size and color into the container store bins that I have upstairs.

There's an app on smartphones that does that to a smaller degree.

But I would love kind of like a little machine, you know, maybe it's the size of a dishwasher and you just put all the Legos on top of it and it sorts them all into the bins.

And so you don't have to do that yourself.

That's the nature, I think, especially for parents at home.

The magic of Lego is that you can take it apart and reassemble it in any possible way.

But that also means you're creating entropy.

The Lego room is always going to have entropy.

And then bringing the entropy back into order is the burden.

And the funny thing is, you know, if you take that into software, that's exactly the same for code, right?

Code also has entropy, like code bases always get worse.

Even if they're stable, then they get worse because the world around the code base is changing new libraries, new operating system and so on.