Stop after five minutes

I think I may have learned something.
If you’re coding with an invisible friend and you find a bug, and you and your friend try to fix it for more than 5 minutes, you need to stop and reset.
I wasted 20 mins last night with Claude going deeper and deeper into code I didn’t understand (Swift+shell) until I eventually did a ctrl-c.
When that happens, 99.9 times out of 10 the fix requires a different viewpoint. In my example, we were going deeper into app permissions management and registration on OSX. I stopped and asked it to instead build a “hello world” of the single feature that was broken. It worked immediately. Two minutes later it comes back with “oh there’s an unmatched xml tag in your plist file”. You don’t say, Mr Infallible AGI coder;-)
In any case, keeping track of time spent problem-solving can speed things up considerably:-)