Your friendly neighbourhood duck 🦆

Do you ever come across a problem and feel totally stumped by it? You ask a coworker, fellow student, or friend for help, but before you finish explaining the problem, you realize the answer all by yourself. It turns out, you just needed to explain the problem out loud to get your brain into problem-solving mode.

As many of you probably already know, this method is called Rubber duck debugging, and I love it!

This method has helped me out so many times through out the bootcamp. I started to do it in the end of my weekly project to get a better understanding of my code, lately I also do it when I get stuck along the way.

I think we can all relate to banging your head against the keyboard because you get errors or the function you just wrote is behaving like a obstinate 6 year old that aint gonna listen to you at all & in the same time you are having a wrestlingmatch with that creepy friend of yours called Imposter syndrome…

You can sit for hours and stare at the code and think that it should work, you did it exactly as you’ve been taught or as that 100th stackoverflow answer you found.

This is where I started to use the magnificant rubberduck! He has helped me find so many missing parantheses and lowercase letters.Another great tip I learnt is to do the rubber ducking with someone who has no experience with coding whatsoever. By explaining your code to someone with no actual understanding of code, you are being forced to break things down into really simplistic terms, in a way that a beginner would understand.So all I want to say is: Rubber ducks are awesome!

And I cant wait to learn more methods that help me grow to a kickass developer!