2 ms·
I think the author hits on an important point under the "Common Ground" section: discussions should be collaborative, not argumentative. If you're trying to mak
by cjcenizal 11y ago
I think the author hits on an important point under the "Common Ground" section: discussions should be collaborative, not argumentative. If you're trying to make a decision with a "me vs. you" mindset, the decision won't get made. Instead, try to frame it as an "us vs. the problem" situation, which helps everyone contribute and work multiple angles to find the best solution, keeping multiple considerations in mind -- including code "quality".
If anyone's interested in more on this, I wrote a short Medium post on other strategies for making better technical decisions: https://medium.com/@cjcenizal/seven-strategies-for-resolving-technical-disagreements-5862a15068fe#.dgudkjr3y https://medium.com/@cjcenizal/seven-strategies-for-resolving....
- deleted 11y ago[deleted]
- humanrebar 11y ago> discussions should be collaborative, not argumentative There's a bit of a prisoner's dilemma here, though. I've tried the collaborative approach with decision makers before only to get grilled, spun into a defensive position, and ultimately dismissed. I think, generally, developers are empathetic to business needs, though they may disagree about the specifics. I find the lack of collaboration comes from the other side of things. Often because of a lack of context from the business side.