you know, sometimes those idiosyncratic ways have a reason for existing because they solve actual problems.
Technical people have a really bad habit of solving for theory rather than practice and they develop this attitude that those who are seemingly entering into odd behavior are just not as good or smart as them.
> you know, sometimes those idiosyncratic ways have a reason for existing because they solve actual problems.
True, but "actual" is a rather low bar. I once worked at a company where a big internal enterprise app controlled a lot of operations, and saw that many of the layers of cruft in the app were because it became the preferred battleground of corporate dysfunction.
One example is that the sales team kept closing deals ('cuz commissions) which were difficult to fulfill, unprofitable, or cannibalized from other assets and activity.
This lead to repeated and increasingly obtuse layers of code for estimating gross-margins, showing values at different interfaces and steps and warning styles, managing and modeling gross-margin reporter/reportee connections and automated alerts and permissions systems where they system would block certain people while e-mailing other people for clicking approval boxes, etc.
Technical people have a really bad habit of solving for theory rather than practice and they develop this attitude that those who are seemingly entering into odd behavior are just not as good or smart as them.