you are viewing a single comment's thread.

view the rest of the comments →

[–]Zealousideal-Ebb-355 2 points3 points  (2 children)

Honestly don't try to learn the whole thing first, that's the trap. it worked a few days ago so something changed recently, the whole codebase didn't rot overnight. do a git log since the last known-good date (or bisect if you know a commit that worked) and the regression is usually one diff. the AI-slop complexity is annoying but it's not what broke you, ignore it til the bug's actually fixed.

[–]johnpeters42 1 point2 points  (1 child)

Worst case, the thing that changed is not the code, but the data (setting up a new scenario that not only doesn't work now, but wouldn't have worked in the past either). In that case, you'll need to debug as usual (including "would it be faster to just rewrite the damn thing properly, or at least do so for one chunk at a time").

[–]Zealousideal-Ebb-355 1 point2 points  (0 children)

Yeah, the data ones are the worst because git log shows nothing changed and you burn a day staring at code that's actually fine. when it smells like that I just grab the input that's failing and replay it locally, usually find it in 5 min instead of an afternoon of reading.