I've found the best way to deal with these types of disagreements is focussing on the requirements. You have one set of requirements in your head (code maintenance, reliability, simplicity) and they have another set in their heads (optimizing whatever it is).

If you can shift the discussion to the _why_ rather than the _what_ I think you will have a better chance of reaching some common ground. A team needs to be pulling in the same direction.