Tom Bilyeu

And so on that, whether it's writing C++ code, being able to identify problems in our blueprints, actually generating 3D assets, none of it just outputs something that's finished.

it outputs something that say is 80% of the way there that breaks under weird circumstances and you have to go figure that out.

But it still speeds you up.

It is incredible.

It is only when people are just like blindly signing off on this stuff or, and I don't know if this is true, but one of the things that I heard was that these companies are actually incentivizing people to just post their code fast.

And so your bonuses are determined by how rapidly you deploy code and

how much you used AI in deploying that code.

I understand what they're trying to train people to do, but show me the incentives and I'll show you the outcome.

If you're not saying I'm incentivizing you to do rapid and like high performance code with limited errors,

then people are just gonna get sloppy and they're gonna push anything and it's up to you to make the most of that.

I'm doing what you told me to do.

So you wanna make sure that you put some sort of restrictions around this actually has to be good.

It's like when you're measuring how fast somebody types.

It's not how fast they can hit the keys.

It's correct words per minute.

So you need to understand like,

How many correct lines of code are you doing?

How many bugs are we finding in your code?

If you make that an important part of this, then people are going to slow down enough to make sure that they actually get that part of it done as well in order to get their bonuses.

So this is a very solvable problem.