Re:When Employees Use Software That IT Hasn’t Approved
by TeMPOraL on Wednesday June 12, 2019 @06:36PM
(#20170059)
> But a "conflict" would be things like anti-malware software making builds fail, not merely making builds 10% slower.
Given developer salaries, a friction like making builds 10% slower is hemorrhaging money. And it gets worse if someone is actually waiting for the software to be delivered, and the amount of money the company gets is correlated to keeping the schedule.
Re:When Employees Use Software That IT Hasn’t Approved
by protomyth on Wednesday June 12, 2019 @02:40PM
(#20167874)
If you have a group of developers, it would probably be a decent idea to have at least one sysadmin dedicated to developer services. It would go a long way to make build deploys go a lot more smoothly.
Re:When Employees Use Software That IT Hasn’t Approved
by maxxxxx on Wednesday June 12, 2019 @10:20PM
(#20171324)
“Being a good software developer doesn't mean you're a good network administrator or good at desktop support.”
Working in IT doesn't mean you're a good network administrator or good at desktop support either :)
Re:When Employees Use Software That IT Hasn’t Approved
by novok on Wednesday June 12, 2019 @06:21PM
(#20169963)
They tend to make builds 2x-3x slower, and the solution usually ends up being 'don't scan git directories and build software' or similar solutions that make them effectively useless anyway.
Being a good software developer doesn't mean you're a good network administrator or good at desktop support. And even if you are, a developer is paid more so it's a poor use of their time.
I'm all for devs having admin access on their own machines, there are too many instances where it's needed, and reasonable exemptions from default policies when they conflict with their work. But a "conflict" would be things like anti-malware software making builds fail, not merely making builds 10% slower.