News for hackers. Stuff that matters.
Re:How I Fight AI Brain Fry by acheron9383 on Sunday November 08, 2026 @06:02PM (#50418490)
I end up in similar situations, the codebase I work on demands a level of professionalism opus5.5 can't muster on the first pass. Code review remains the bottleneck. Usually I approach it like a code review, reading through and as I find things I markup the code, then afterwords I have the agent collate all the feedback and we discuss and it re-implements. Usually I can simplify and improve a lot in like 3 passes.

One thing that speeds up the reviews and improves my ability to find issues and provide guidance is having the agent work on better review guides (think an html page rendered locally, with object diagrams, decisions/assumptions, animations of data flow if it makes sense, whatever). Those in hand I can read the codebase faster and talk against that document too. I think the end result is better code than I could previously write by hand, in probably 5x the speed.

Usually I can't do more than two projects in parallel though.

Re:How I Fight AI Brain Fry by sollewitt on Sunday November 08, 2026 @07:06PM (#50419180)
Yeah, that makes a ton of sense, I'm going to try this - I particularly like the idea of making animations of data flow.
Re:How I Fight AI Brain Fry by zarldev on Sunday November 08, 2026 @08:28PM (#50419813)
Event Catalogue is something I have been using for this https://www.eventcatalog.dev/ only thing is no longer MIT license.
Re:How I Fight AI Brain Fry by matltc on Monday November 09, 2026 @12:08PM (#50428358)
By far the skill I use the most is one I wrote called "resolve-review" from back in the 4.6 days. Just uses gh CLI and graphql to get inline comments, which I key with standard tags like nit/fixit. So during review, I open vscode so I can have an lsp and jump around refs more easily (only reason I still have vscode installed; frozen at v1.110.1 with ai completely disabled and I haven't got around to getting the same setup in neovim), leave comments, send review, then resolve review. I'm sure one could have hooks or scheduled tasks listening for this but it's good enough for me. Working on a thing to build a pipeline of such work, which I describe in a top-level comment.

I do not have any pressure to deliver anything (amateur), so I can only imagine how much it must suck for anyone on that hamster wheel given how much it bothers me. If anyone wants to work on something like this, drop me a line; I miss working with people.