Rubber Duck Coding Method

If you don t have a coding buddy but you totally should you can leverage the rubber duck problem solving technique to figure out problems all by yourself or with the benefit of the greater internet community.

Rubber duck coding method.

Many other terms exist for this technique often involving different usually inanimate objects or pets. Suddenly your perspective is different. Vlog 46 today i cover rubber duck debugging. After all the rubber duck doesn t know what you know.

We are not. What it is and why you should always steer clear of programmers sitting at their desk talking to rubber ducks or other little toys. Fortunately ducky scripts may be converted into binary to embed them then into firmware. Place rubber duck on desk and inform it you are just going to go over some code with it if that s all right.

Beyond the rubber duck. The act of speaking out loud forces you to slow down and be more precise and thoughtful in your explanations. It is precisely this that makes rubber duck debugging effective. While it appears to be an innocuous usb thumb drive when it is plugged into a computer it instead registers itself as a usb keyboard on the system and fires off a keystroke payload at lightning speed.

In software engineering rubber duck debugging is a method of debugging code. The usb rubber ducky is an awesome device for penetration testing and general mischief. When you go through code line by line explaining each part to the rubber duck you pay closer attention to the small details. The rubber duck debugging method is as follows.

And that s super important. The psychological shift outside of yourself and into the rubber ducky changes everything. Onward to bigger problems. Beg borrow steal buy fabricate or otherwise obtain a rubber duck bathtub variety.

For usb rubber ducky there is a whole website with a friendly interface which lets you create any scripts for your device online. Rubber duck problem solving. 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 themselves to explain it line by line to the duck.