one evening i asked the agent to audit my own app's code end to end, no changes, just tell me where it is slow or dumb. the api, the database layer, the plugin, the whole thing. the report came back with a list of real things: queries that could be batched, a service that re-read config per call, and a few places where the same data got embedded twice on every request. the fun part started when i said make all of it, and then prove each change actually helped.
the rule i set was that nothing gets merged on vibes. every optimization got measured before and after, and a couple of the fancy suggestions were thrown back out because the speedup was noise. the database work was the only one that was meaningfully faster, because the app's query layer was re-fetching joined tables per item instead of once per page. fixing that cut the slow path more than all the cleverness combined. threading was genuinely not worth it here, the app spends its time waiting on storage and an index scan, not on cpu.
the habit worth keeping is the verify step. git saved us at least twice, and the whole project rolls back to a known good state when an experiment loses. most of what makes a personal app feel fast is fewer round trips, not more parallelism. the after picture: same features, less code, and a search page that stops stuttering on big vaults.