Now you must be thinking, ‘What do rubber ducks and development have in common?’, other than being the start to a potentially cheesy joke, it's actually a lot more than you think… stay with me.
‘Rubber ducking' is short form for ‘rubber duck debugging' a term coined in the 1999 book ‘The Pragmatic Programmer’. In this book it explains having a physical rubber duck on a developers desk is one of the best tools for a coding dilemma.
Why? It forces developers to simply talk to the object about their final code outcome and the issues they are currently experiencing. By walking through the issue line by line they can see their problem from a bird's eye view, thus helping them to solve the issue in an alternate way.
Now, before you run out and buy your new desk pal, this theory can be used with a physical rubber duck, another developer or even a project manager. I know from my side, as someone who is not skilled with writing code, problems are seen from a logistical standpoint and solutions are offered based on this.
If all else fails and the rubber duck starts conversing with you, it may be time to close down the computer for the day and return with fresh eyes in the morning.
At Develo we bridge the gap between project managers and developers in order for our clients to fully understand developer terms, issues and fixes. Knowledge shared between us helps our client and agency relationships all around.
Have a problem you’d like us to Rubber Duck for you?