This involved calling engineers at their desks and offering workshops where they got some continental breakfast and to try out some very expensive IC design tool.
The company had a web application written in ColdFusion that had a bunch of forms to fill out each time a phone call or email exchange was performed with a lead. Enterprise sales would use this information to move sales through the pipeline.
I got bored really quickly of tabbing through the page and the repeat data entry based on call or email outcome. So I found a windows macro tool and wrote 5-10 macros that handled 80% of all call outcomes, making it trivial to add details.
Ideally, the web application would just get this kind of automation. However, some of the macros were campaign specific--they just didn't do it.
When my manager saw how I was pulling off the call volume and results, (which were modest--it was still largely cold calling), everyone on the team got a license to the macros and I was asked to share the macros around.
They were all RCGs or recent masters grads, so it wasn't really a problem. But it immediately set a floor for "why are you typing that and using your mouse to finish this call? We have a tool to do that" kind of thing.
The incredibly-slack labor market this describes wasn't reflective of my experience or that of anybody I knew as of ten years ago. After a decade of tightening in that market, this is even less true.
As I said, it's likely bimodal: certain geographies/verticals/perhaps specialties probably still afford tech workers a 1990s-like level of market power.
But it's worth pointing out that what you're describing is not remotely the norm for at least some dense subnetwork of labor (of which I'm a part). Further, it's potentially the case that entry into this labor market is accessible to those who are currently in the looser market, especially as IMO talent doesn't account for the entirety of the gap.
It's also pretty weird to "hate" that others have managed to find meaning in their work, and discuss the manner in which they do so. I don't get much enjoyment out of cars, but if I noticed that I _hated_ it when others talked about cars and insisted that they treat them only as generic conveyances, I'd probably want to do some self-reflection around my emotional state.
To re-use your metaphor, it'd be like a car nut telling you your quality as a person is less for not liking cars as much as they do.
The initial comment was "to do your job well, you should do X". The response was "I hate this type of comment. I don't care about doing my job well".
That seems like a pretty bizarre reaction. If someone said "it's hard work, but you should focus on [XYZ] to ensure your code is well-tested", and someone responded "I hate it when people talk about how to make code more robust. I don't care about doing my job well", would you find that a reasonable response as well? Or in response to parenting advice, "I hate this type of comment. I don't want to have kids". It seems to me that the implicit context for how to do your job well is....people who care about doing their job well?