Re:Gas Town's Agent Patterns, Design Bottlenecks, and Vibeco...
by johnmaguire on Friday January 23, 2026 @12:18PM
(#46735043)
In a recent Yegge interview, he mentions that he often throws away the entire codebase and starts from scratch rather than try to get LLMs to refactor their code for architecture.
Re:Gas Town's Agent Patterns, Design Bottlenecks, and Vibeco...
by kami23 on Friday January 23, 2026 @12:55PM
(#46735504)
This has been my best way to learn, put one agent on a big task, let it learn things about the problem and any gotchas, and then have it take notes, do it again until I'm happy with the result, if in the middle I think there's two choices that have merit I ask for a subagent to go explore that solution in another worktree and to make all its own decisions, then I compare. I also personally learn a lot about the problem space during the process so my prompts and choices on us sequent iterations use the right language I need to use.
Re:Gas Town's Agent Patterns, Design Bottlenecks, and Vibeco...
by d1sxeyes on Friday January 23, 2026 @12:56PM
(#46735510)
Honestly, in my experience so far, if an LLM starts going down a bad path, it’s better just to roll back to a point where things were OK and throw away whatever it was doing, rather than trying to course correct.
I've written two seperate moderately-sized codebases using agentic techniques (oftentimes being very lazy and just blanket approving changes), and I don't encounter logic or off-by-one errors very often if at all. It seems quite good at the basic task of writing working code, but it sucks at architecture and you need occasional code review rounds to keep the codebase tidy and readable. My code reviews with the AI are like 50% DRY and separating concerns