Dan Shipper

I think it was Claude Opus 3.7.

And we were testing it before it came out.

And when we test models, me and Kieran often are on a video call together and just chatting back and forth.

And he was like, I don't think I have to look at the code anymore.

And so we were trying that.

And we were like, holy shit, this is crazy.

And this is like maybe...

it's probably almost a year ago now um yeah and that then filtered into the rest of our company and we started being like i don't think we need to look at the code anymore and that became a thing that we were doing but everyone else was like that's crazy um and now it seems you know pretty much like that's the case pretty normal now yeah it's pretty normal it's pretty normal um

And out of a lot of his experience with that came compound engineering, which is the idea that in normal engineering, each feature you build makes it harder to build the next feature.

Because the code base grows in complexity.

All the complexity is interdependent usually.

You have all these tests.

You have a bunch of stuff that all depends on each other.

Even in a modular code base, it still is like that.

And in combat engineering, what you're trying to do is make each feature easier to build than the last.

And that is by...

as you do things, you compound the learnings from each feature into the next one.

So like each bug that you find or each issue that you make, or if you're proof, like each first principle of building YJS applications that you miss, you like compound that into a research, into a, into your knowledge base and your repo so that every engineer has access to this.

Um,

So, and link and share it in the chat.