3 ms·
>As a dev, corp laptops are usually so locked down as to be useless, i.e. unable to install dev tools etc. In a past life writing my company, which was a .NET
by fatnoah 4y ago
>As a dev, corp laptops are usually so locked down as to be useless, i.e. unable to install dev tools etc.
In a past life writing my company, which was a .NET shop, was acquired by a large company that used Macs for everyone except salespeople. They didn't provide Macs to anyone on my team, so we had to use the Windows boxes that were so locked down we had to get exceptions for everything. While we were successful in getting Visual Studio and other tools added to the exception list, were weren't successful in getting our compiled software added to the list. i.e. we literally couldn't run the software were were acquired to create.
For the short term, we discovered that anything done in WSL (Windows Subsystem for Linux) was completely ignored by endpoint security, so that let us work around many local issues for the 18 months or so it took us to get Macs for work.
- GordonS 4y agoAnother "trick" I've used before is to run everything inside a Hyper-V VM on a locked-down Windows box. Locking down machines makes sense, but won't someone please think of the developers?!