(2) is rubber duck debugging (written in a condescending way). The point of rubber duck debugging is the duck isn't talking back, or questioning why the code e

(2) is rubber duck debugging (written in a condescending way). The point of rubber duck debugging is the duck isn't talking back, or questioning why the code exists, or why the project exists, or suggesting different programming approaches - it just sits there while you work through explaining it and listening to you.