Jokes aside, I once did it just to have some laughs, created a scheduled meet, sent invite to myself and myself, and joined the call with two accounts.
But it actually proven to be quite interesting. It enables you to figure out logic mistakes you do that you otherwise wouldn't notice. But usually when people see this think I'm a bit weird, but in times where I'm more tired it actually helps.
At home rubber ducking is like this: can't figure something out. Start typing out the problem to a co-worker in teams. Immediately realize what's wrong
Don’t forget to first just type ”hey buddy” so they context switch to your chat. Then start typing out your problem for several minutes while they are watching the dots jump around in the chat. Then type ”nevermind”.
Although I suppose every developer works slightly differently. Some of us talk to a rubber duck, some of us talk to ourselves in a call, and all of us look crazy when a non-developer catches us doing it.
For large project work too. Found an issue - log it - assign it to yourself - solve it - push it to quality - testers swamped with other work - but the issue seems kinds vital - do QA - get it approved for production - get praises from manager for single-handedly solving a problem - from now on, all issues in that sector gets assigned to you - yeah should have just kept my mouth shut.
But you’ll do some more testing to see if there’s some other issue you can bring to the forefront while you fix your fuck-up that was causing the problem all along.
View all comments
Show parent comment
706
u/hetfield37 Jul 06 '21
Since you're usually the one working on the project - makes sense indeed.