TL; DR:
- Give agents constraints, not just tasks.
- Better output doesn't mean better methodology.
- You're still responsible for defining done.
- No live stream this week -- I am on-call!
My Agents Are Building. Am I Giving Them What They Need?
I've been building a creature-breeding game called Evo Habitat Zero with AI agents. One works on the game mechanics. Another works on art and assets. And honestly? It's been pretty cool watching a game come together this way.
It's also been rocky.
There have been moments where I look at what happened and think, "Holy crap. How did we get down this path?" Builds were crashing. Simple assets were enormous. The art was improving, but getting there could take a lot of iteration. And the mechanics agent seemed to think it was finishing a game that I definitely wouldn't call done.
The interesting part isn't just that agents made mistakes. Some of those mistakes pointed directly at guidance I hadn't given them.
This content is only available for members.
Become a Member
Or subscribe to the free Dev Leader Weekly newsletter for C#, .NET, and software engineering content every Saturday.