3 ms·
Learning to argue both sides can help. One of the reasons I'm (fairly) good at persuading people or at least expressing my rationale even if I fail to persuade
by Jtsummers 6y ago
Learning to argue both sides can help. One of the reasons I'm (fairly) good at persuading people or at least expressing my rationale even if I fail to persuade is that I have long practiced the counterarguments in my head (and often with others). It helps that I was very introverted and introspective as a teen and college student. That is, I don't start from a position of "I'm right" but a position of "What if I'm wrong", and then work towards a set of arguments that either go against my initial position or sufficiently justify it. At that point, I feel comfortable presenting my ideas to others.
With enough practice, this becomes something you may be able to do on the fly. If you're a relatively slow thinker (I often am), it can help to set the pace. Make enough noise when you're thinking something through that others can't steamroll over you.
--------
Learn to express your assumptions. If I go into a design meeting and I say, "X is good and how we should do it." I should back that up with my assumptions. "We're targeting an embedded, resource constrained, real-time system so we should use an appropriate language that gives us tight control over the runtime and memory usage. Therefore, I recommend we use C, given that our team is very familiar with it."
--------
A reason for stating assumptions is also that many debates are based on a misunderstanding. You're arguing against each other's positions because you enter with different assumptions. Using a real experience: A colleague strongly objected to the use of recursion in programs. When we finally worked it out, it wasn't that he didn't like recursion full-stop, it was that his experience was almost exclusively with real-time, embedded systems where recursion was avoided for good reason (along with things like heap allocation). He'd internalized so that it was almost a reflex to be anti-recursion. Once we were able to realize why he argued against recursion, though, he was willing to relax his stance given different circumstances (writing desktop applications, or similar environments with relatively few constraints).
If you state your assumptions it gives people a better chance to realize where you're coming from. And then you can start asking for theirs. Though maybe not using the word "assumption". Ask "why": "Why do you object to inheritance ever being used?" or the counter position "Why do you want a 20-deep inheritance hierarchy?". What about either of those positions makes either the design or the maintenance easier or harder, what are the trade-offs. Maybe they selected a design based on ease and speed of implementation, or ease of testing, or ease of maintenance. But each of those can have tradeoffs with the other so get them (and answer this yourself, don't just expect others to answer these) to state their priorities. Then, even if you lose the final argument, you can at least understand why a decision was reached (difference in priorities, different in experiences, whatever).