Rubber Duck Debugging: History and Benefits 橡皮鴨調試：歷史和優勢

注：機翻，未校對。

Discover the origins of rubber duck debugging, why it works, and why it has become so popular among programmers.
了解橡皮鴨調試的起源，它為什么有效，以及為什么它在程序員中如此受歡迎。

Debugging code can be a frustrating and time-consuming process, with programmers often spending hours or even days trying to identify the root cause of a problem. However, a technique called rubber duck debugging has become a popular and effective method for programmers to quickly identify and fix issues in their code. The technique involves explaining code line-by-line to an inanimate object, usually a rubber duck, which can help programmers break the code down into smaller, more manageable pieces and identify where the problem is occurring. Discover the origins of rubber duck debugging, why it works, and why it has become so popular among programmers.
調試代碼可能是一個令人沮喪且耗時的過程，程序員經常花費數小時甚至數天來試圖確定問題的根本原因。然而，一種稱為橡皮鴨調試的技術已成為程序員快速識別和修復代碼中問題的一種流行且有效的方法。該技術涉及向無生命的對象（通常是橡皮鴨）逐行解釋代碼，這可以幫助程序員將代碼分解成更小、更易于管理的部分，并確定問題發生的位置。了解橡皮鴨調試的起源，它為什么有效，以及為什么它在程序員中如此受歡迎。?

What is Rubber Duck Debugging?
什么是橡皮鴨調試？?

Rubber duck debugging is a common method used by programmers to debug code by explaining it to an inanimate object, usually a rubber duck. The concept behind rubber duck debugging dates back to the 1990s and has since become a popular debugging technique used by software developers around the world.
橡皮鴨調試是程序員通過向無生命對象（通常是橡皮鴨）解釋代碼來調試代碼的常用方法。橡皮鴨調試背后的概念可以追溯到 1990 年代，此后已成為全球軟件開發人員使用的流行調試技術。

The origins of rubber duck debugging can be traced back to a book called “The Pragmatic Programmer: From Journeyman to Master” written by Andrew Hunt and David Thomas. In the book, the authors described a technique called “rubber duck debugging,” which involved explaining code line-by-line to a rubber duck.
橡皮鴨調試的起源可以追溯到 Andrew Hunt 和 David Thomas 撰寫的一本名為“The Pragmatic Programmer： From Journeyman to Master”的書。在書中，作者描述了一種稱為“橡皮鴨調試”的技術，該技術涉及向橡皮鴨逐行解釋代碼。
?
Why do Programmers Use Rubber Duck Debugging?
為什么程序員使用橡皮鴨調試？
?
The idea behind rubber duck debugging is that when a programmer is stuck on a problem, explaining the code to someone else, or in this case, an inanimate object, can help them identify the root cause of the issue. By describing the problem to the rubber duck, the programmer is forced to break down the code into smaller, more manageable pieces, which can often help them identify the source of the problem.
橡皮鴨調試背后的想法是，當程序員遇到一個問題時，向其他人解釋代碼，或者在這種情況下，向一個無生命的對象解釋代碼，可以幫助他們確定問題的根本原因。通過向橡皮鴨描述問題，程序員被迫將代碼分解為更小、更易于管理的部分，這通常可以幫助他們確定問題的根源。
?
Rubber duck debugging is based on a technique called “active listening,” which involves actively listening to someone else to fully understand their point of view. By using this technique to explain code to a rubber duck, the programmer can gain a better understanding of the problem and potentially identify the root cause of the issue.
橡皮鴨調試基于一種稱為“主動傾聽”的技術，該技術涉及積極傾聽他人以充分理解他們的觀點。通過使用這種技術向橡皮鴨解釋代碼，程序員可以更好地了解問題，并可能確定問題的根本原因。
?
Why Does Rubber Duck Debugging Work?
為什么橡皮鴨調試有效？
?
One of the primary benefits of rubber duck debugging is that it helps to identify the root cause of the problem. By explaining the code line-by-line to a rubber duck, the programmer is forced to break the code down into smaller, more manageable pieces. This can help them to identify where the problem is occurring and what may be causing it. By gaining a better understanding of the code, programmers can more easily identify and fix issues.
橡皮鴨調試的主要好處之一是它有助于確定問題的根本原因。通過逐行向橡皮鴨解釋代碼，程序員被迫將代碼分解為更小、更易于管理的部分。這可以幫助他們確定問題發生的位置以及可能導致問題的原因。通過更好地理解代碼，程序員可以更輕松地識別和修復問題。
?
It can also save time and increase productivity! When a programmer is stuck on a problem, they may spend hours or even days trying to find the root cause of the issue. However, by explaining the code to a rubber duck, they can often identify the problem much more quickly. This can save time and increase productivity, allowing the programmer to move on to other tasks more quickly.
它還可以節省時間并提高生產力！當程序員遇到問題時，他們可能會花費數小時甚至數天的時間試圖找到問題的根本原因。但是，通過向橡皮鴨解釋代碼，他們通常可以更快地識別問題。這可以節省時間并提高生產力，使程序員能夠更快地繼續執行其他任務。
?
Rubber duck debugging can also encourage collaboration and communication among team members. When a programmer is stuck on a problem, they may turn to their colleagues for help. By explaining the code to a rubber duck, they may also be explaining it to their colleagues, who can offer suggestions and ideas for solving the problem. This can promote collaboration and communication, helping to build stronger teams and improve overall productivity.
橡皮鴨調試還可以鼓勵團隊成員之間的協作和溝通。當程序員遇到問題時，他們可能會向同事尋求幫助。通過向橡皮鴨解釋代碼，他們也可能向同事解釋代碼，他們可以提供解決問題的建議和想法。這可以促進協作和溝通，有助于建立更強大的團隊并提高整體生產力。

?Finally, rubber duck debugging can help to catch errors before they become larger problems. By identifying and fixing issues early on, programmers can prevent them from snowballing into larger, more complex problems down the line. This can save time and reduce the risk of more significant issues occurring later on.
最后，橡皮鴨調試可以幫助在錯誤變成更大的問題之前發現錯誤。通過及早識別和修復問題，程序員可以防止它們像滾雪球一樣越滾越大，變成更大、更復雜的問題。這可以節省時間并降低以后發生更重大問題的風險。
?
Why is Rubber Duck Debugging Popular?
為什么橡皮鴨調試很受歡迎？
?
The concept of rubber duck debugging has since become popularized in the programming community, with many programmers using it as a common debugging technique. It has even been incorporated into some integrated development environments (IDEs), such as Microsoft Visual Studio, which includes a rubber duck debugging feature.
橡皮鴨調試的概念從此在編程社區中流行起來，許多程序員將其作為一種常見的調試技術。它甚至被整合到一些集成開發環境（IDE）中，例如Microsoft Visual Studio，其中包括橡皮鴨調試功能。

In addition to its usefulness as a debugging technique, rubber duck debugging has also become a popular meme within the programming community. The concept of using a rubber duck to explain code has been used in various programming jokes and memes, with many programmers referring to their rubber duck as their “debugging buddy.”
除了作為調試技術的有用性外，橡皮鴨調試還成為編程社區中流行的模因。使用橡皮鴨來解釋代碼的概念已被用于各種編程笑話和模因中，許多程序員將他們的橡皮鴨稱為他們的“調試伙伴”。

Rubber duck debugging is a simple but effective technique used by programmers to debug code. By explaining the code line-by-line to an inanimate object, such as a rubber duck, programmers can break down the code into smaller, more manageable pieces, and potentially identify the root cause of the problem. Rubber duck debugging can save time, increase productivity, encourage collaboration and communication among team members, and help catch errors before they become larger problems. As a result, this technique has become widely popularized in the programming community and is a valuable tool for programmers of all levels of experience.
橡皮鴨調試是程序員用來調試代碼的一種簡單但有效的技術。通過向無生命的對象（如橡皮鴨）逐行解釋代碼，程序員可以將代碼分解為更小、更易于管理的部分，并可能確定問題的根本原因。橡皮鴨調試可以節省時間，提高生產力，鼓勵團隊成員之間的協作和溝通，并幫助在錯誤成為更大的問題之前發現錯誤。因此，這種技術在編程社區中得到了廣泛的普及，對于各種經驗水平的程序員來說都是一個有價值的工具。

via: