So I'm a mid-level manager at a company with a few hundred developers.
The more developers you hire, the higher the chance you'll start collecting people with obscure (but usually reasonably easy to satisfy) tool preferences. You know, the guy who changes his IDE to emacs key bindings, the guy who does all his e-mail using mutt when everyone else uses gmail, the girl who uses a Dvorak keyboard layout, the guy who insists he works best on a 1024x768 screen, and so on. Having tried a variety of industry tools and thought about about how you work best is usually a good sign[1].
Their favourite tools aren't my favourite tools, but they work for me so if they're not happy, I'm not happy.
The bait and switch is we adopted a tool that would keep IRC users happy, and it dropped IRC support.
[1] Although I keep my settings conservative, as it's hard for others to pair program or assist you with problems if they can't operate your computer
The more developers you hire, the higher the chance you'll start collecting people with obscure (but usually reasonably easy to satisfy) tool preferences. You know, the guy who changes his IDE to emacs key bindings, the guy who does all his e-mail using mutt when everyone else uses gmail, the girl who uses a Dvorak keyboard layout, the guy who insists he works best on a 1024x768 screen, and so on. Having tried a variety of industry tools and thought about about how you work best is usually a good sign[1].
Their favourite tools aren't my favourite tools, but they work for me so if they're not happy, I'm not happy.
The bait and switch is we adopted a tool that would keep IRC users happy, and it dropped IRC support.
[1] Although I keep my settings conservative, as it's hard for others to pair program or assist you with problems if they can't operate your computer