I'm trying to tackle it by writing it down and waiting for others to finish with some decent success.
I'm trying to tackle it by writing it down and waiting for others to finish with some decent success.
Writing it down won't get you too far, imho. Because you probably still will be in rush just to read what you noted down and eventually miss the chance to learn from others. It's all about listening first.
There was a thread here on HN recently, titled "People with Greater Intellectual Humility Have Superior General Knowledge".[0] I think it's pretty relevant here in this topic. Intellectual humility goes a long way I'd say :-)
Sometimes technical thoughts can be literally founded on faulty assumptions and will teach you nothing unless providing another anecdote of a conceptual mistake is instructive.
Listening in bikeshedding conversations is a wise maneuver, though. Save your forceful thoughts for actual problems.
Start it when you start talking, and periodically make it a habit to check ("How long has it been since someone else talked?").
If it's been too long, wrap up your thoughts and pause a while before launching into the next bit.
It's usually obliviousness ("I didn't notice anyone else", in my personal experience), but it can feel very rude to others ("I didn't want to listen to anyone else").
All part of soft skills. We all get better together.
If it's really important, I'll remember it.
Apology speaks directly to your impulsive mind, a kind of self-inflicted peer pressure mechanism.