Realistically, what justification is there any more for working on somebody else's machine, being force to use their config? Ok, if your machine explodes and you need their's for a bit fine. But in the long run, the amount of times where you need to actually edit some code by typing on another person's machine should be vanishingly small.
I'm all for standards when it comes to collaborating on code. But when it comes to text editors, vim configs, even using emacs (get out your crosses, holy water and sliver bullets), it shouldn't really matter from my perspective.
This, I don't want anyone else's disgusting unwashed hands on my keyboard or mouse. I work with a guy who regularly walks out of a bathroom stall and back to his desk, bypassing the sink entirely. He tried taking over my machine, I was like hell no. So I get a rep for ocd germaphobe, big deal.
How do people who like to customize their environment do pair programming? I belong to that group, and I like the idea of pair programming, but I've never had the chance to try it in practice...
Far more common these days, I think, than actually typing on another person's keyboard is sharing an account on a server (physical or virtual). Not that that's a great practice.
This reminded me that more often than I'd like, people want me to debug their dev setup on local Vagant VM (I'm an Op and among other I partially support the development environment). I hate that, to use the different layout and not having my tools ans aliases.
Tried to tell them to use dev env on some local shared machine, where it's easier to setup and manage, but they refuse and want to do these things in a local VM.
I just try to say that there might be semi-legit cases when you must go and use other person's laptop.
I'm all for standards when it comes to collaborating on code. But when it comes to text editors, vim configs, even using emacs (get out your crosses, holy water and sliver bullets), it shouldn't really matter from my perspective.