The only real objection I have to this as a term is that it's too easy to confuse with "rubber ducking": https://en.m.wikipedia.org/wiki/Rubber_duck_debugging
this post was submitted on 22 Nov 2023
44 points (95.8% liked)
Programming
17374 readers
257 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities [email protected]
founded 1 year ago
MODERATORS
My dad tells a similar story of an offshore oilrig person giving a tour to some C-Suite type people. His alarm goes off, and he pauses the tour to throw an oily rag on the floor. 5 minutes later the rig supervisor person steps out of their office, looks around, shouts about oily rags and health&safety risks, then goes back into their office.
With a similar "punchline" about giving the supervisor something obvious to complain about
So, perhaps call it an "oily rag"?
I remember seeing a comic once about two devs, one complaining that this senior always puts lots of nitpicky comments on her code review, and the other replies that he always makes one obvious mistake, so the senior can point it out and feel like they've done their job
Do your thing internet, cos I cannot find it
This works a lot of the time with the people that don't really care about the review. With those that do it won't