Rubber Duck debugging

“I’ve done everything right, so why doesn’t it work?”

We’ve all been there. You’ve crafted a script or expression that should do exactly what you intended. Except it doesn’t. You stare at the code and scrutinize every expression, but the error still eludes you. In cases like these, Rubber Duck debugging, or Rubberducking, can be a very helpful technique.

What is Rubber Duck debugging?

When you apply Rubber Duck debugging, you explain your code and its expected result step by step in natural language. As the name implies, your counterpart in this exercise is typically a rubber duck. Of course, you can also use other objects, pets, or even non-technical coworkers.

While you explain your code, you’ll (hopefully!) run into a step where the intended action you’re explaining doesn’t match with what’s actually happening. Quack! Eureka! Problem solved.

Get your own Bitmetric Rubber Ducky!

Whether you are already applying this technique, or want to start using it, you can now augment and enhance your experience with your very own Bitmetric Rubber Ducky.

How can you get one?

Attend any of our onsite events, keep an eye out on our blog posts and LinkedIn page for upcoming events.

Quack quack! 🦆

More from the Bitmetric team

Bitmetric Qlik Support

Keep your Qlik environment running smoothly with proactive support that prevents issues before they appear. Available on flexible monthly plans. Learn more.

Qlik vs Power BI Series

See how Qlik and Power BI perform when theory meets reality. Three apps rebuilt, every step examined. Learn more.