+1 I agree with waiting. In fact I'm personally coming around to the point of view that 90% of verbal technical discussions miss a key point which becomes very evident on reflection and/or are an inefficient use of time(N developers * x minutes and so on). You can be much more effective by writing a doc about the subject, reviewing it over email/Slack with an in-person discussion if required.
I cannot stress how important writing is. Writing is thinking. And often writing what you intend to argue in a meeting is an effective way to solidify your point.
If you think you can convince someone by reasoning about it from the seat of your pants don’t be surprised when your colleagues are not convinced.
This is good advice!
Although sometimes you have to bite the bullet and accommodate your hands-on improvisational types and have a good old-fashioned spit-balling session!
