This is why it's good practice to just never use MM/DD or DD/MM dates anywhere. 2-Mar or 2-MAR is nearly as terse but much less ambiguous. The only other date format I default to is YYYY-MM-DD (i.e. 2019-03-02). It sorts well and, by putting the year first, doesn't pick a side in the MM/DD or DD/MM battle. It just lists the terms in descending significance.
One of our customer integrations uses all of MM-DD-YY, YY-MM-DD and DD-MM-YY for a date input. Took us quite a few man-hours to figure out why our integration layer failed so often.