Comment

Comment by jenniferhooley

Without going through the following flow I very quickly end up with nitty recurring micro bugs or interaction "gunk" and 10's of thousands of lines of pointless code that bloats out the code-base and agent's context.

plan -> approve -> agent codes -> review code -> cleanup and pointing to specific skills/agents depending on what the issues are and some manual instructions pointing to specific lines of code-> agent codes -> review code -> final cleanup -> ship.

Working on a 3d sims-like video game I cannot get away with much less than that flow outside of very small features. I have (like all of us I assume) tried moving forward over weeks of not code reviewing and only plan reviewing, and it's amazing how badly things fell apart, I ended up having to reset weeks of work and ended up knocking out like 50K loc for the exact same features and zero bugs instead of constant bug (or just interaction/latency gunk cropping up everywhere) cleanup slowly escalating and agents needing to take hours to build anything.

Might find this interesting: https://earendil.com/posts/measuring-code-sloppiness/

No comments yet

Be the first to share your thoughts.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton