|
|
|
|
|
by Tade0
99 days ago
|
|
> Well it’s not just a “text predictor” is it? It is, by definition, design and architecture a system that produces believable text. Here's a task to give it which pulls the veil right off: Ask it to add tests to a piece of code where code coverage is 100%, but it doesn't actually test functionality 100%. You'll start seeing nonsense sooner or later. |
|
The “just a text predictor” framing was fair a couple years ago but hasn’t kept up. Current models can genuinely identify untested edge cases even when coverage is 100%. You're definitely using the latest and greatest models?
The architecture started as next-token prediction, sure, and yes, human judgment is still required, but that judgment is being captured and integrated too. Every time millions of people use these models, their feedback feeds the next round of improvements.
Also, these models don’t need to replace your best engineers to be disruptive. They just need to outcompete the bottom of the bell curve. For a lot of junior-level work, we’re already getting close.