Rain Paharia

And I'm like, there's always been this activation energy.

We have to go read the documentation and stuff.

And so what I instead ended up doing with this is that I took an existing project that I had, which I felt like was a good fit for Kani.

And I just asked Cloud Opus 4.5 to, hey, come up with a few properties that we can verify that way.

And it just did that.

And I'm like, now I understand how this stuff works and what the limitations are and stuff.

And just like, like, there are so many ways you can kind of use this stuff to, to go like increase the level of rigor in our software.

And honestly, it really bothers me that the dominant narrative is the whole like slop white code stuff.

Right.

Because like, or infrastructure engineers, there's so much more you can get out of it.

I mean, the thing I will say personally is like having a culture where writing things down is valued.

is like, you know, it is like a real multiplier here.

And so, uh, I mean, our oxide, like I'm, I'm very happy that, you know, all of this work that we do, like we now have a new way to gain leverage from, from all this writing work that, you know, we are culturally do, uh, if you're, if you're at a place that, you know, maybe it doesn't have as strong rigorous like requirements or like, you know, isn't as committal as, as oxide where we ship hardware or whatever.

Um,

I would still consider, like, you know, doing work to write things down and produce good documentation, good design documents, because, like, at least the current generation of LLMs, like, really like that.

And so, you know, like, kind of, you know, get a little more disciplined, right, with some of these things, right?

So, yeah, that's what I would say.

Like, write things down.

Honestly, this is kind of the advice I would give.

I would say practice writing.