An issue I've been running into a lot is that me and colleagues are discussing how to do a certain thing in the field of software development, e.g. security. The team leans towards a certain approach that they think is secure. However, from experience I know this approach is not secure. Now I try to explain that it is in fact not secure, but fail to convince them about it not being secure. Often this is due to disbelief on their side ("if this isn't safe, then how does anyone make anything secure?"). It doesn't help much that the most vocal person in my team is also my senior by a longshot.
At this point, I feel like I only have 2 options (or a combination thereof):
- Be stubborn and keep trying to explain it isn't secure.
- 'Co-operate' in implementing the feature, only to immediately show it isn't secure by showing an actual exploit as soon as the security features that are supposed to secure the application are implemented.
I feel like the former option is a good way to get myself hated if I persist for too long, and people are just going to stop taking it seriously after some point. Meanwhile, the latter option feels like an inglorious waste of time, used only out of lack of an alternative.
This persuasion problem also occurs regularly with people other than my current colleagues (and with different subjects), so it is not strictly a 'compatibility issue' between me and them.
General tips to help explain things better or help persuade people are definitely appreciated, but I feel like I'm missing something fundamental here.