I've worked in several jobs, and there is usually a time when the sysadmin(s) and the developers should have "the talk" about the IT infrastructure.
From the sysadmins viewpoint, most of the users need Office apps on Win10, with access to the web and a mail server. The responsibility is to make all that work securely, that is with backups and without malwares.
From the developers viewpoint, they need performance, low-level access to their hardware (ex: direct access to USB), admin-level rights for some tasks, sometimes on another OS.
How to find a solution that fits everyone (both sysadmins and developers)?
Most of the time, what I see is developers doing what they want on their side, until either:
- the sysadmin asking for admin access to "control the whole infrastructure"
- the sysadmin asking for complete reinstallation of another kind of this OS (e.g. change of Linux distribution, so "everyone has the same system")
- the sysadmin asking to virtualize the developers environment, so that they run their OS on top of a monitored "workplace approved" OS.
This leads to some arguments, as the developers don't see any benefit for them to change their whole work system. I've seen a "split" when the developers refuse and are then isolated on a subnetwork of the company with one of the developers in charge.
Do you know some acceptable compromise that permits both side to work together without split or resentment from any side?