4h ago

Bend Creator Warns AI Agents Harm Productivity And Introduce Bugs

——0——
Original post
OPTaelin#1047Taelin@VICTORTAELIN

Status update: I've been on/off AI agents in the last few days and it is a verifiable truth that every day I didn't use AI I was more productive. Also, Bend2's C/Metal compiler codebase is a clusterfuck right now. I regret letting AI agents write it. All tests pass, and GPU performance is mind-blowing, so the core architecture works. Yet, it has a LOT of bugs. Anything not covered by the tests is a coin toss. This is actually impressive, because, in many parts of the codebase, the right solution was actually the simplest one, yet, the agents STILL managed to find a way to make it work just for the tests. The level of reward hack these agents output is actually impressive I can't even be mad. It is also ironical because that's the very problem that Bend's proof system was supposed to solve, but Bend is in TypeScript, not in Bend. I'm disappointed I didn't write Bend in itself, and now I feel an immense urge to do so. But the clock is ticking . . . Still, I do not think Bend is worth launching without a the GPU compiler being solid, because the closest competitor, Lean, is actually extremely good. For the very nature of the project, it would be embarrassing to have bugs at launch. Regarding Ai, I now believe using current gen AI agents in production codebase is harmful and a massive mistake. That doesn't mean no agents at all, but agents work best when they don't touch critical code. Debugging, researching, providing insights, scripts / tools, or anything that doesn't touch code you will maintain in the wrong term. But if you merge AI code without reading, you're going to have a bad time. Speaking of experience I'm working 10h/day on SupGen and the remaining time on Bend2

10:29 AM · May 26, 2026 View on X
Reposted by
Taelin#1047@VICTORTAELIN
POSTTaelin#1047Taelin@VICTORTAELIN

Status update: I've been on/off AI agents in the last few days and it is a verifiable truth that every day I didn't use agents, I was more productive. I still attribute that to how slow they are, and my own inability to multi-task efficiently. The magic is there but the slowness doesn't let it cross the threshold where they actually make me faster, and I still dislike the whole thinking paradigm.

About Bend2: honestly, the C/Metal compiler codebase is a clusterfuck right now. I regret letting AI agents write it. All tests pass, and GPU performance is mind-blowing, so the core architecture works. Yet, it has a LOT of bugs. Anything not covered by the tests is a coin toss. This is actually impressive, because, in many parts of the codebase, the right solution was actually the simplest one, yet, the agents STILL managed to find a way to make it work just for the tests. The level of reward hack these agents output is actually impressive I can't even be mad.

It is also ironical because that's the very problem that Bend's proof system was supposed to solve, but Bend is in TypeScript, not in Bend. I'm disappointed I didn't write Bend in itself, and now I feel an immense urge to do so. But the clock is ticking . . .

Still, I do not think Bend is worth launching without the GPU compiler being solid, because the closest competitor, Lean, is actually extremely good, so we need a big differential. Yet, due to the very nature of the project, it would be embarrassing to have bugs at launch.

Regarding AI, I now believe using current gen AI agents in production codebase is harmful and a massive mistake. That doesn't mean no agents at all, but agents work best when they don't touch critical code. Debugging, researching, providing insights, scripts / tools, or anything that doesn't touch code you will maintain in the long term. But if you merge AI code without reading, you're going to have a bad time. Speaking from experience

I'm working 10h/day on SupGen and the remaining time on Bend2

5:36 PM · May 26, 2026 · 64.2K Views
Bend Creator Warns AI Agents Harm Productivity And Introduce Bugs · Digg