Nobody Should Be Using Rubber Duck🦆 Debugging in 2023

Summary

The article argues that Rubber Duck Debugging is an outdated practice in 2023 and advocates for collaborative problem-solving and knowledge sharing within software development teams.

Abstract

The article titled "Nobody Should Be Using Rubber Duck🦆 Debugging in 2023" suggests that software engineers should move beyond the solitary technique of explaining code to an inanimate object, such as a rubber duck, to resolve issues. Instead, the author emphasizes the importance of leveraging teamwork to improve code quality and facilitate learning. The author posits that by working closely with colleagues, through practices like pair programming, developers can share problems and solutions, thereby enhancing team knowledge and resilience. The article criticizes the isolation of rubber duck debugging, stating that it represents a missed opportunity for collaborative growth and that developers should strive to become integral team players who contribute to the collective intelligence of their organization.

Opinions

Rubber Duck Debugging is seen as an inefficient method that can be replaced by more effective collaborative techniques.
Describing problems to a rubber duck is equated to avoiding interaction with colleagues, which limits learning and problem-solving within a team context.
The author believes that if Rubber Duck Debugging solves a developer's problem, it suggests the

The alternative is to 10x your code

Even the best software engineers have bad days. Logic can feel impenetrable and difficult to process, yet you need to get that feature out of the door. Yesterday.

What to do?

Choosing the right technique at the right time is vital, as is knowing a variety of tools that you can choose when you just can’t see the way through or around your technical problem.

Duck Out Of Here.

Using rubber duck debugging is in lieu of describing your problems to a co-worker.

You’re not working in a team, and you’re avoiding speaking to people

Instead of pair programming and learning from one another you are in your silo. Your problem remains your problem, and learning is limited to you. Yeah, a couple colleagues should read your work in a code review but they just skim it before “LGTM”.

What a wasted opportunity.

Ducking The Issue

A problem shared is a problem halved. If you use rubber duck debugging and it is successful you probably didn’t have a big issue in the first place. You knew the answer and just needed to think it over.

If you’re not thinking things over as a software developer, you might just be a ticket pusher. Nothing wrong with ticket pushers but shouldn’t you think about raising your standards and becoming a vital team player?

Look up, not down

Work as a team, or don’t bother

We need to work together to deliver features. If you’re sick one day (month, year, leave) organizational knowledge is the most important thing. If you aren’t spreading your knowledge throughout the team and working to make yourself redundant you won’t get that promotion. You won’t deserve it and frankly, those who work to protect their knowledge at the expense of the team deserve to be fired.

There: I said it

Nobody Should Be Using Rubber Duck🦆 Debugging in 2023

The alternative is to 10x your code

Rubber Duck Debugging?

Duck Out Of Here.

Ducking The Issue

Work as a team, or don’t bother

About The Author

Join Medium with my referral link — The Secret Developer

Read every story from The Secret Developer (and thousands of other writers on Medium). Your membership fee directly…