&quot;Vim&#x27;s default are indeed dumb, but what you described is not a vim-specific problem. Walk into any room full of coders and try to use their computers; you&#x27;ll discover tons of weirdness that can&#x27;t be explained by anything except by a desire to be treated like a princess.&quot;<p>Yes, shame on those evil coders for wanting to use their own computers in a manner which they find most enjoyable and productive!  They must be assimilated!  Give me a break.<p>&quot;Things like rebinding basic shortcuts,&quot;<p>Again, give me a break.  Developers should be allowed to configure their individual machines in any way they wish.  Different people work differently.<p>&quot;reversing the scroll direction (Mac users will get this),&quot;<p>When you&#x27;ve worked on platforms for decades where the scroll direction works one way, then end up on a platform where it is reversed, what is wrong with changing the new system to work the way you are used to?  Yeah, I might decide to get used to the differences, or I might change it because I prefer it the old way, but who cares?<p>&quot;swapping Cmd&#x2F;Ctrl,&quot;<p>again, who cares -- it&#x27;s their machine.<p>&quot;using some obscure shell&quot;<p>I also see no problem with this -- if they prefer it, just let them.<p>&quot;or even infecting other people&#x27;s machines with some haphazardly scp&#x27;d dotfiles.&quot;<p>This is a legitimate complaint, if the person is leaving stuff behind that screws up the other person&#x27;s computer.  But if the person is expected to work on other peoples machines, then I think a reasonable solution could be worked out.  You should try to defer as much as reasonably possible to the person who the machine belongs to.  On the other hand, if you are asking someone else to do work on your machine, it seems reasonable to let them copy some dotfiles in order to help them do the work -- as long as they don&#x27;t affect your stuff.<p>&quot;This kind of overcustomization is fine if you live in a basement and work on a project alone.&quot;<p>I don&#x27;t buy the &quot;overcustomization&quot; label.  Yes, it is possible to spend too much time customizing things (if, for example, it prevents you from getting your actual work done).  However, programmers can make themselves <i>much</i> more efficient by many of these customizations.  Different people have different ways of working, and they have different jobs.  Vanilla configurations of things like editors are fine, but the ability to customize exists for a reason -- you can make your job easier and yourself more efficient by customizing your tools.<p>&quot;As soon as you become a part of a team, please stop. You&#x27;re making cooperation unnecessarily hard and spending company time on an optimization that isn&#x27;t.&quot;<p>I&#x27;ve worked on <i>many</i> different development teams over the years.  At all of those jobs, it was an extremely rare thing to even do development on someone elses computer.  Everyone uses their own.<p>&quot;I sometimes joke that coders who refuse to conform to the industry standards should wear a tiara as an indication they are, indeed, unique snowflakes free from the usual social expectations. It seems to work.&quot;<p>What &quot;industry standards&quot; are you referring to?  Is there an ISO standard for vim keybindings?  Please.  Also, I don&#x27;t think the whole &quot;Princess&quot; analogy is fair.  Just because someone has their own way of working doesn&#x27;t make them self-absorbed and shallow.<p>(edited for better formatting)