[text] Theres a thing called Rubber duck debugging in which a programmer explains the code to a rubber duck in hopes of finding the bug Ultrafacts.tur cosrmos liteofdavo Kierenwalkerpds monobeartheater absorr ultrafacts 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. Im reblogging because think ts 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 SIMPLEI AM GOING BLINDY AS APROGRAMMER 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 AWALL OR SOMETHING WHEN THEY FIGURED OUT THE PROBLEM IN THEIR CODE so thats the function of a rubber duck k at a startup and part of the onboarding package you get when you first start working here now includes a rubber duck. We also have a bigger version of the duck for the exira hard problems. Sometimes one duck doesnt cut it and you need to borrow your neighbors to get more ducks on the problem. One time we couldnt figure out why something wasnt working right s0 we assembled the counsel of ducks and by the grace of the Duck Gods were we able to finally come to a solution. These ducks have saved many lives and should be respected for the heroes they are
in Debugging, Linux, Programming