Rubber Duck Debugging
From journeyman to master by andrew hunt and david thomas.
Rubber duck debugging. This is where the concept of rubber duck debugging comes in. Rubber duck debugging is intended to cure you of the tunnel vision that programmers often fall victim to by forcing you to acknowledge and explain each pieceits as if youre looking at the code with a fresh set of eyes all over again. Rubber duck debugging the rubber duck debugging method is as follows. The principles behind why it works for programmers can also be applied to growth marketers and entrepreneurs that feel completely stuck.
Nellingegneria del software viene indicata come rubber duck debugging o rubber ducking una pratica di debugging che consiste nello spiegare riga per riga il funzionamento di un programma ad un oggetto inanimato come appunto una papera di gomma. In it a programmer would carry around a rubber duck and debug their code by forcing themselves to explain it line by line to the duck. The legend of the master programmer with a rubber duck on her desk who talked her little duck through her code as she debugged. Rubber duck debugging is a reference to a story in a programming book called the pragmatic programmer.
A rubber duck in use by a developer to aid code review in software engineering rubber duck debugging is a method of debugging code. Rubber duck debugging is more than just a way of helping programmers to deliver a finished product. Learn how in this post on why you should simply go and duck yourself. To be clear the rubber y and duck y ness of the object dont matter its just important that its not you.
Place rubber duck on desk and inform it you are just going to go over some code with it if thats all right. If you can imagine a figure that works. Lidea infatti e che descrivendo dettagliatamente il funzionamento atteso del programma ed. Beg borrow steal buy fabricate or otherwise obtain a rubber duck bathtub variety.
The name is a reference to a story in the book the pragmatic programmer in which a programmer would carry around a rubber duck and debug their code by forcing themself to explain it line by line to the duck1.