{"id":18950,"date":"2023-04-04T10:49:51","date_gmt":"2023-04-04T14:49:51","guid":{"rendered":"https:\/\/carleton.ca\/webservices\/?p=18950"},"modified":"2024-06-26T09:29:03","modified_gmt":"2024-06-26T13:29:03","slug":"quack-the-code-the-power-of-rubber-duck-debugging","status":"publish","type":"post","link":"https:\/\/carleton.ca\/webservices\/2023\/quack-the-code-the-power-of-rubber-duck-debugging\/","title":{"rendered":"Quack the Code: The Power of Rubber Ducking"},"content":{"rendered":"\n
\n
\n\n
\n
\n
\n

\n Quack the Code: The Power of Rubber Ducking\n <\/h1>\n \n \n <\/header>\n\n <\/div>\n\n <\/div>\n\n <\/div>\n<\/section>\n\n\n\n

Why are we talking about rubber ducks on the Web Services blog? Turns out, rubber duck debugging is an actual thing that developers do…!<\/p>\n\n\n\n

As part of our Agile working process<\/a>, we have daily meetings where we update each other on what we are working on. And we talk about any issues we are encountering. During a recent meeting, one of our developers said he had \u201crubber ducked\u201d some code with some other developers… Hmmm, Mike, did you just say you \u201crubber ducked?!\u201d<\/p>\n\n\n\n

\"Our<\/figure>\n\n\n\n

What is rubber duck debugging?<\/h2>\n\n\n\n
\n

Rubber ducking is a technique that programmers use to debug code. They explain it line by line to a rubber duck. Or any entity that understands almost nothing about the problem. It’s like having a sounding board to bounce your ideas off of. This helps to simplify and clarify problems. And by taking it step-by-step, the solution often presents itself.<\/p>\n

How does it work?<\/h2>\n

Explaining something to someone helps you to better understand it. It lets you see things from a different perspective. And you may uncover or catch something that you missed before.<\/p>\n

Legend has it that Andrew Hunt and David Thomas (a couple of programmers from days gone by), would carry around an actual rubber duck. When they got stuck, they\u2019d explain their code to the duck. But not just the code itself. They\u2019d also describe their goals and what they wanted the code to do. And they would do this in as clear and simple terms as they could.<\/p>\n

Have you ever been in a situation where you are explaining a problem to a friend\u2026? And before you even finish, you\u2019ve come up with the solution. Same idea. The bonus with rubber duck debugging is that you don\u2019t even need to disturb anyone.<\/p>\n

To solve problems and to learn things, it often helps to teach them to someone else. This is the premise behind rubber duck debugging. Unfortunately, the duck doesn\u2019t give you the solution… But by talking things out and explaining issues, you clarify and uncover solutions.<\/p>\n

Try it Out<\/h2>\n

Rubber duck debugging is a popular technique in the programming world, but maybe it’s not just for programmers… Anyone who is working through a complex problem or trying to brainstorm a creative solution could benefit from it.<\/p>\n

So, the next time you’re feeling stuck on a problem, grab a rubber duck (or your pet) and give it a try. You may be surprised at just how helpful it is. Quack quack!<\/p>\n

Sign up for our newsletter<\/a> for more web tips and updates \ud83d\ude42<\/p>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

Why are we talking about rubber ducks on the Web Services blog? Turns out, rubber duck debugging is an actual thing that developers do…! As part of our Agile working process, we have daily meetings where we update each other on what we are working on. And we talk about any issues we are encountering. […]<\/p>\n","protected":false},"author":2,"featured_media":18955,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":"","_links_to":"","_links_to_target":""},"categories":[369],"tags":[],"class_list":["post-18950","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-carleton-cms"],"acf":{"cu_post_thumbnail":""},"_links":{"self":[{"href":"https:\/\/carleton.ca\/webservices\/wp-json\/wp\/v2\/posts\/18950","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/carleton.ca\/webservices\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/carleton.ca\/webservices\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/carleton.ca\/webservices\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/carleton.ca\/webservices\/wp-json\/wp\/v2\/comments?post=18950"}],"version-history":[{"count":1,"href":"https:\/\/carleton.ca\/webservices\/wp-json\/wp\/v2\/posts\/18950\/revisions"}],"predecessor-version":[{"id":20616,"href":"https:\/\/carleton.ca\/webservices\/wp-json\/wp\/v2\/posts\/18950\/revisions\/20616"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/carleton.ca\/webservices\/wp-json\/wp\/v2\/media\/18955"}],"wp:attachment":[{"href":"https:\/\/carleton.ca\/webservices\/wp-json\/wp\/v2\/media?parent=18950"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/carleton.ca\/webservices\/wp-json\/wp\/v2\/categories?post=18950"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/carleton.ca\/webservices\/wp-json\/wp\/v2\/tags?post=18950"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}