AI-assisted coding gives programmers an illusion of control while the actual code produced is often not truly understood by anyone, much like pulling a slot machine lever.
Jeremy Howard compares AI coding tools to gambling slot machines: crafting prompts, MCPs, and skills feels like skill and control, but pulling the trigger produces a stochastic result and code nobody fully understands. ✦ AI generated
Jeremy Howard · Machine Learning Street Talk · 2026-03-03 · original ↗
starts at this moment · 47:53
“You have to tell us about coding.”
The thing about AI based coding is that it's like a slot machine in that you have an illusion of control. You know, you can get to craft your prompt and your list of MCPs and your skills and whatever. And then but in the end, you pull the lever, right? You put in the prompt and something comes back.
verbatim transcript · starts at 47:53
47:53days of great enthusiasm am I using today? Are my customers using today? am I making money from today? Almost all the money is being made by influencers, you know, or by the companies that produce the tokens. The thing about AI based coding is that it's like a slot machine in that you you have an illusion of control. You know, you can get to craft your prompt and your
48:22list of MCPs and your skills and whatever. And then but in the end, you pull the lever, right? You put in the prompt and something comes back and it's like cherry cherry. It's like oh next time I'll change my prompt a bit. I'll add a bit more context. Pull the lever again. Pull the lever again. It's the stochastic thing. You get the occasional win that's like, "Oh, I won. I got a
48:48feature." So, it's got it's got all these hallmarks of like loss disguised as a win. um somewhat stochcastic uh feeling of control, all the stuff that um gaming companies try to engineer into their gaming rooms. Now, none of that means that AI is not useful, but gosh, it's hard to tell. >> I know. And and Rachel, just just to be clear to she also said that one of the
49:16hallmarks of gambling is that you kind of delude yourself that you have some awareness of what's going on, but but actually you don't. But let let's do the bull case a little bit, though. So because I do I do think in restricted cases it it is it is very useful and these are cases where we understand and and we can place constraints and specification but um even in those cases
49:34you could argue on the one hand that we're not you know we're not going to be unemployed anytime soon because you just do more work on the addiction thing I've noticed that so I've had 14-hour claude code marathon sessions and and I actually feel addicted to it. It's like a slot machine, you know. It It really is. >> Been there, too. Absolutely. >> Yeah, I know. It's And just I've never
49:53felt more drained writing code. I actually need to take a rest afterwards, like a few days rest because it completely >> was crap, you know. Yeah, definitely. I've had some successes, right? And so in fact, we've spent the last couple of years building a whole product based around where we know the successes are going to be, which is when you're working on reasonably small pieces that you can fully understand and that you
- ·Crafting prompts, MCPs, and skills feels like control
- ·Pulling the lever produces a stochastic result
- ·Code generated is often not truly understood by anyone
- ·Developers invest effort in prompt engineering
- ·But the output is fundamentally unpredictable
- ·Analogy: similar to pulling a slot machine lever