4 ms·
> Most of the resistance I've observed amongst engineers is resistance to change generally. Most engineers I've known are enthusiastic when given the opportuni
by autoexec 5mo ago
> Most of the resistance I've observed amongst engineers is resistance to change generally.
Most engineers I've known are enthusiastic when given the opportunity to play around with a new toy. What they don't like is anything being forced on them.
There's nothing irrational about that. They've often invested a lot of time into optimizing their workflows.
I've also found that if something actually makes their work easier, you will never have to twist their arm to make them use it. They'll apply it everywhere it helps. They'll even try using it in places and in ways it was never intended for. If they're digging in, you likely haven't made a very compelling case for your changes.
- andrekandre 5mo ago> What they don't like is anything being forced on them raises hand (n=1), i'm fine to use it when i need it, but the derangement by management about it is a total put-off and unnecessary (and in the end counter-productive)
- paradox460 5mo agoExactly this >Here's a new editor we made Cool, looks interesting, I'd love to use it more >We're forcing you to use it I hate it
- AlexeyBelov 5mo agoYeah. Nobody mandated Jetbrains products, almost every developer I know decided for themselves. Actually, it was the opposite: I remember asking a company I once worked for to buy me a license. Took 6 months for them to finally agree. Now my monthly allotment of tokens is way bigger than the price of that license, and it was given freely.
- ryandrake 5mo agoYep, if a toy was that good, then everyone would be begging their managers to use it, not the other way around. Nobody ever had to force me to use keyword coloring, code formatters, source control, or a bug tracker.