Paul Dix

And I use Cloud to make it.

And I didn't actually then take the time to go through and like refactor a bunch of other spots in the code that kind of were impacted by the change.

we got a few more weeks down the line and then and everything seemed to be fine and then we started doing more extensive testing and basically there were like these weird failures that only occurred when we were like under load or under resource constraints or certain like timing issues we didn't know what it was right and last week you know we had multiple engineers myself included like trying to figure out what it was and of course all of us are like

using agents to try and help and investigate the problem.

And basically, by last Thursday, I was like, man, we're just spinning our wheels here.

It's like everybody is in the AI casino pulling the levers on the AI slot machine, slop machine.

hoping, you know, hoping for manna from heaven to come down and, uh, triple sevens.

Right.

Exactly.

And the problem is like, none of us were actually getting anywhere.

And I was like, okay, I'm just going to pull the plug on all of this.

And I'm just going to go back to basics and audit everything myself by hand, like personally.

And I think, uh,

On reflection, I think this was due to a few different problems.

But before I cover that, that experience tells me, well,

If we are going to take 60,000 lines of vibed up code or it's not totally vibed up, right?

Because it's not like there was absolutely no supervision.

It wasn't like build me an app and I have no idea what's underneath the thing.

But still, it's 60,000 lines of kind of vibed up code and an engineer has to support it.

This is Rust code too, right?