I think there should be a compromise. Use your own config but be ready to switch quickly to a more "common" config and know how to use it (whatever common means in your context, just adapt to your team).
For example I use i3, and I switch ctrl and caps lock. During my first pair programming experience my colleague was struggling with all that and I was feeling quite guilty ("maybe this need to fine-tune everything is just immature after all"). After this I made sure to be able to switch quickly to a "vanilla" Gnome setup.
Although coming back to Gnome after using i3 is quite easy since the Gnome paradigm is quite universal, there are some alternative "configs" that I am afraid to adopt, such as exotic keyboard layouts ("bepo" in french instead of "azerty"). Losing the ability to type on this de facto standard layout would be quite problematic.
I listen to SomaFM's Drone Zone channel on noise-cancelling headphones when I program. It broadcasts "drone" music – no lyrics, very little rhythm, melody or harmony – the music concentrates mainly on sound texture. And of course, no ads. Can't recommend it enough.
It is not that slow. On my machine Vanilla Emacs starts in 0.1 second. With my 12 years-old config, it starts in 0.4 second. Emacs 27 pre-init system made it even faster.
For example I use i3, and I switch ctrl and caps lock. During my first pair programming experience my colleague was struggling with all that and I was feeling quite guilty ("maybe this need to fine-tune everything is just immature after all"). After this I made sure to be able to switch quickly to a "vanilla" Gnome setup.
Although coming back to Gnome after using i3 is quite easy since the Gnome paradigm is quite universal, there are some alternative "configs" that I am afraid to adopt, such as exotic keyboard layouts ("bepo" in french instead of "azerty"). Losing the ability to type on this de facto standard layout would be quite problematic.