2 ms·
> Now, I absolutely get why people have bad attitudes towards IT. IT is often unfairly biased against users. After all, the only users they interact with most o
by TeMPOraL 3y ago
> Now, I absolutely get why people have bad attitudes towards IT. IT is often unfairly biased against users. After all, the only users they interact with most of the time are morons, and that paints an unfair stereotype. Like, for example, the stereotype that those users are morons: it's not the user's job to use a computer, it's the user's job to do whatever their job it, and the computer is a tool to do that. Yeah, users should know a little bit about how to use their tools, but that's a little difficult to enforce.
The big part of people's bad attitude towards IT is that, from user perspective, they're noticeable only when they suddenly make it more difficult or impossible for the user to actually do their job. And they do it often enough that they're seen as an outside force that's at best annoying, at worst dreaded.
Now sure, the typical user may not know the other side of the coin, and in many cases the annoyances are legitimate from the POV of safety and effectiveness of the company as a whole. But then, occasionally IT seems to not see the costs either.
I'm biased here, but I have this negative bias towards IT despite being rather experienced and savvy computer user, because I've been on the receiving side of changes that make it hard for software devs to do their work, in companies that make money selling software.
My favorite example is Windows Defender "realtime protection" - a functionality that adds a noticeable cost to individual I/O operations (writes) on any file except those on one of several exclusion lists (excluding by location in the filesystem, excluding by the process making the I/O call, etc.). This feature has really bad interaction with typical software dev work - version control, building software, running tests, and other things a dev does constantly, tend to do a lot of tiny I/O operations, and they all suffer the penalty. This can easily make all your actual work activities take 2-3x longer - or more, when you account for the disproportional distraction it causes[0].
Now, the corporate IT decides the endpoint machines are not allowed to add additional exclusions to the list, even if otherwise the user has local administrative rights. The list is fixed, contains mostly system stuff, and all your dev tooling and source code is not on it. I wonder if anyone tried to calculate the total cost of this one decision - money lost by software releases being effectively delayed 2x, and in associated extra salaries for one of the most expensive employees in any tech company? Is it worth it, relative to whatever this decision saves? Is it worth sticking to it, and ignoring tickets from software dev begging for help, and/or replying to them that the company will reimburse them for a laptop cooling pad?
--
[0] - https://xkcd.com/303/ https://xkcd.com/303/. Or, when single `git add` of a file takes 2 seconds instead of near-instant, that slowly makes you avoid touching it. `git commit` taking 1 minute instead of few seconds (for executing post-commit hooks) is the difference between being in the flow and browsing HN. Etc.