You're viewing a single thread.
Aside from "learning to spell hypnotized or just trusting your phone knows better than you," there are a bunch of tricks we use.
- Staring at it and going over the code path
- Talking to a proverbial duck
- Going out for a proverbial cheeseburger
- Sleeping on it
Half of these tricks force the brain to stop confirming and start seeing, which is our biggest error source. The rest of these tricks let the problem ruminate in our subconscious which is sometimes really good at solving shit.
1, 3 and 4 (in that exact order) have almost always gotten things moving again. rubber ducking it just feels "forced" to me.
I talk to myself almost constantly, even when not programming. Rubber ducking is second nature to me now. Though, IDK which came first.
You can just talk to one of your more inept coworkers.
Haven't heard of the proverbial cheeseburger.. gonna stare at this phrase for a bit.
If you don't get it, go for a proverbial cheeseburger
I dunno, I don't like unnecessarily interacting with strangers. I'm gonna go sit in another room and tinker with something else for now.