Source For more posts like this, CLICK HERE to follow Ultrafacts
Some of you are reblogging because you think its funny that programmers would talk to ducks. I’m reblogging because I think its funny picturing a programmer explaining their code, realizing what they did when they explain the bad code, then grabbing the strangling the duck while yelling “WHY WAS THE FIX THAT SIMPLE!? AM I GOING BLIND!”
AS A PROGRAMMER I CAN TELL YOU THAT THIS IS EXACTLY WHAT YOU FUCKING DO WE HAD TO BAN THE DUCKS FROM MY CLASSES BECAUSE EVERYONE WOULD FLIP THE DUCK OR THROW IT AT A WALL OR SOMETHING WHEN THEY FIGURED OUT THE PROBLEM IN THEIR CODE
It doesn’t have to be a duck. It can be anything: duck, teddy bear, action figure, cardboard cutout, coworker who stands there going, “mn… mmhmm…” every 30 seconds…
All the matters is the act of breaking down your problem into a form that can be described verbally. It uses different pathways in your brain than the same one you’ve been treading bare for the past hour while tearing your hair out and gives your subconscious the opportunity to insert new connections and insights.
'Verbally' is super important! Just thinking the explanation doesn't use the same parts of your brain as opening your mouth and stumbling through it, no matter how silly it might look.
Other ways to trigger subconscious problem-solving: take a walk, take a shower, sleep
Source: I am a programmer. This is what I do all day.