| I cope by doing very little customization. Maximize the defaults first. Work that way where it makes sense. What this has done is improve on overall flexibility. At times, my role is one where I do end up using other people's environments. First thing I do is get them to tell me, then work that way as much as is possible. Some peak efficiency is left on the table, but the impact is usually minor and I can optimize somewhere else and do just fine. Dependence on muscle memory is a double edged sword. If one does not environment hop much, it is worth it. Where that needs to happen, exercising "stretch" to work differently can be equally worth it. Not sure there is a free lunch here. I find state changes difficult. When it is reverted to default, or my preference, the others are not happy, and it takes time to put it all back, and sometimes more time to remember how to do those things and debug having done them. |