Talking to an inanimate object like a rubber duck is a debugging technique called rubber duck debugging. The term was shaped in 1999 by Andrew Hunt and David Thomas - the authors of the book The Pragmatic Programmer.

Why some programmers talk to rubber ducks

A very simple but particularly useful technique for finding the cause of a problem is simply to explain it to someone else. The other person should look over your shoulder at the screen, and nod his or her head constantly (like a rubber duck bobbing up and down in a bathtub).

Rubber duck/Inanimate object:<ul><li>very patient listener</li><li>has infinite time </li><li>is always available</li><li>holds back on feedback </li></ul> Person/Colleague/Friend<ul><li>not always available</li><li>might not have time/patience to listen to the whole problem</li><li>might give advice if the problem does not want to solve itself</li></ul>

Rubber Duck vs. Person

Explaining a problem (it doesn't even have to be a bug in programming) helps to look at the problem from a different perspective. That helps to better understand what one is trying to accomplish and often the error is almost obvious while explaining it to someone else.

Why it works

When a bug gets you stuck, explain it to a rubber duck.

“One of the most significant books in my life.” –Obie Fernandez, Author, The Rails Way “Twenty years ago, the first edition of The Pragmatic Programmer completely changed the trajectory of my career. This new edition could do the same for yours.” –Mike Cohn, Author of Succeeding with Agile, Agile Estimating and Planning, and User Stories Applied “. . . filled with practical advice, both technical and professional, that will serve you and your projects well for years to come.” –Andrea Goulet, CEO, Corgibytes, Founder, LegacyCode.Rocks “. . . lightning does strike twice, and this book is proof.” –VM (Vicky) Brasseur, Director of Open Source Strategy, Juniper Networks The Pragmatic Programmer is one of those rare tech books you’ll read, re-read, and read again over the years. Whether you’re new to the field or an experienced practitioner, you’ll come away with fresh insights each and every time. Dave Thomas and Andy Hunt wrote the first edition of this influential book in 1999 to help their clients create better software and rediscover the joy of coding. These lessons have helped a generation of programmers examine the very essence of software development, independent of any particular language, framework, or methodology, and the Pragmatic philosophy has spawned hundreds of books, screencasts, and audio books, as well as thousands of careers and success stories. Now, twenty years later, this new edition re-examines what it means to be a modern programmer. Topics range from personal responsibility and career development to architectural techniques for keeping your code flexible and easy to adapt and reuse. Read this book, and you’ll learn how to: Fight software rot Learn continuously Avoid the trap of duplicating knowledge Write flexible, dynamic, and adaptable code Harness the power of basic tools Avoid programming by coincidence Learn real requirements Solve the underlying problems of concurrent code Guard against security vulnerabilities Build teams of Pragmatic Programmers Take responsibility for your work and career Test ruthlessly and effectively, including property-based testing Implement the Pragmatic Starter Kit Delight your users Written as a series of self-contained sections and filled with classic and fresh anecdotes, thoughtful examples, and interesting analogies, The Pragmatic Programmer illustrates the best approaches and major pitfalls of many different aspects of software development. Whether you’re a new coder, an experienced programmer, or a manager responsible for software projects, use these lessons daily, and you’ll quickly see improvements in personal productivity, accuracy, and job satisfaction. You’ll learn skills and develop habits and attitudes that form the foundation for long-term success in your career. You’ll become a Pragmatic Programmer. Register your book for convenient access to downloads, updates, and/or corrections as they become available. See inside book for details.

problemsolving

Problem Solving

computerscience

Computer Science

“One of the most significant books in my life.” –Obie Fernandez, Author, The Rails Way “Twenty years ago, the first edition of The Pragmatic Programmer completely changed the trajectory of my career. This new edition could do the same for yours.” –Mike Cohn, Author of Succeeding with Agile, Agile Estimating and Planning, and User Stories Applied “. . . filled with practical advice, both technical and professional, that will serve you and your projects well for years to come.” –Andrea Goulet, CEO, Corgibytes, Founder, LegacyCode.Rocks “. . . lightning does strike twice, and this book is proof.” –VM (Vicky) Brasseur, Director of Open Source Strategy, Juniper Networks The Pragmatic Programmer is one of those rare tech books you’ll read, re-read, and read again over the years. Whether you’re new to the field or an experienced practitioner, you’ll come away with fresh insights each and every time. Dave Thomas and Andy Hunt wrote the first edition of this influential book in 1999 to help their clients create better software and rediscover the joy of coding. These lessons have helped a generation of programmers examine the very essence of software development, independent of any particular language, framework, or methodology, and the Pragmatic philosophy has spawned hundreds of books, screencasts, and audio books, as well as thousands of careers and success stories. Now, twenty years later, this new edition re-examines what it means to be a modern programmer. Topics range from personal responsibility and career development to architectural techniques for keeping your code flexible and easy to adapt and reuse. Read this book, and you’ll learn how to: <ul> <li>Fight software rot</li> <li>Learn continuously</li> <li>Avoid the trap of duplicating knowledge</li> <li>Write flexible, dynamic, and adaptable code</li> <li>Harness the power of basic tools</li> <li>Avoid programming by coincidence</li> <li>Learn real requirements</li> <li>Solve the underlying problems of concurrent code</li> <li>Guard against security vulnerabilities</li> <li>Build teams of Pragmatic Programmers</li> <li>Take responsibility for your work and career</li> <li>Test ruthlessly and effectively, including property-based testing</li> <li>Implement the Pragmatic Starter Kit</li> <li>Delight your users</li> </ul>Written as a series of self-contained sections and filled with classic and fresh anecdotes, thoughtful examples, and interesting analogies, The Pragmatic Programmer illustrates the best approaches and major pitfalls of many different aspects of software development. Whether you’re a new coder, an experienced programmer, or a manager responsible for software projects, use these lessons daily, and you’ll quickly see improvements in personal productivity, accuracy, and job satisfaction. You’ll learn skills and develop habits and attitudes that form the foundation for long-term success in your career. You’ll become a Pragmatic Programmer. Register your book for convenient access to downloads, updates, and/or corrections as they become available. See inside book for details.

David Thomas is an accomplished writer whose work has resonated with readers around the world. David Thomas has published several books that explore a range of topics, from fiction to nonfiction, and has received critical acclaim for the ability to weave compelling narratives. David Thomas's writing style is known for its depth and authenticity, and has earned quite a loyal following of readers.

David Thomas

Andrew Hunt is an accomplished writer whose work has resonated with readers around the world. Andrew Hunt has published several books that explore a range of topics, from fiction to nonfiction, and has received critical acclaim for the ability to weave compelling narratives. Andrew Hunt's writing style is known for its depth and authenticity, and has earned quite a loyal following of readers.

ANDREW HUNT & DAVID THOMAS

Similar ideas

Taking an outside perspective

Reason for a Dead End 2. Users have strayed off the beaten track