3 ms·

Or, in the corporate information systems world, we have to wait for the half-dozen security and monitoring systems to get done scanning memory and blocking whil

Or, in the corporate information systems world, we have to wait for the half-dozen security and monitoring systems to get done scanning memory and blocking while painstakingly logging to the clould. Only then do you get to watch a catatonic UI thread idly wait for every last piece of the underlying software to load.

analog31 2y ago
Yes and everything hangs because the security software is the last to load.
- wizzwizz4 2y ago
  Ctrl+Alt+Delete, log off, then mash space to cancel the logoff. Kills the security software while leaving the rest of the system running. (Windows provides APIs to prevent this, but nobody writing "security" software uses them: in the Age of AI, I expect this to get even worse.
ffsm8 2y ago
Not only do they forbid devs to use Linux on their dev machines, they then proceed with cb.exe etc. Nothing shows how they value your time quiet as much as these artificial slowdowns they love to introduce. (Along with gigantic privacy issues, as it allows the employer to essentially look at a live feed of your desktop whenever they want) I could understand it if your device needed special access (VPN to prod etc), but you usually can't do that either from the dev machines - and need to first connect to a virtual machine (via browser or rdp) to be able to do that...
- bregma 2y ago
  Well, we use Linux dev machines but IT has loaded them up with enough panopticon software that several times a week for an hour or so I can not get enough CPU or resident RAM to do productive work. But at least there are no forced system reboots at inconvenient times during the work day.
  - MathMonkeyMan 2y ago
    At a previous job they offered Linux laptops (yay!), but... - umask was not 022, so installing pretty much anything with `sudo make install` would fail, as would some software. - Running nmap caused an alert to phone home to IT, who would nag me on slack. - Opening well-known ports to my LAN (like 22) caused an alert to IT. - An "agent" program ran constantly, often using 100% of a CPU. The system overall had about 45 minutes of battery life. - Various system settings were overridden by a sysctl.d/ file that was regenerated by the agent at boot. Fortunately I know how ASCII sorting works and could produce a file that overrode the overrides. - Various capabilities (CAP_...) were disabled for my sudoer user. It wasn't that bad, and IT was helpful, but it was a persistent annoyance. Maybe what happened is somebody googled "how to harden Linux" and then just made everything on the first page of results company policy.
    - DmitryOlshansky 2y ago
      At my work they would also disable ptrace in the kernel and require you to explain why need it

analog31 2y ago

Yes and everything hangs because the security software is the last to load.

wizzwizz4 2y ago
Ctrl+Alt+Delete, log off, then mash space to cancel the logoff. Kills the security software while leaving the rest of the system running. (Windows provides APIs to prevent this, but nobody writing "security" software uses them: in the Age of AI, I expect this to get even worse.

ffsm8 2y ago

Not only do they forbid devs to use Linux on their dev machines, they then proceed with cb.exe etc. Nothing shows how they value your time quiet as much as these artificial slowdowns they love to introduce. (Along with gigantic privacy issues, as it allows the employer to essentially look at a live feed of your desktop whenever they want) I could understand it if your device needed special access (VPN to prod etc), but you usually can't do that either from the dev machines - and need to first connect to a virtual machine (via browser or rdp) to be able to do that...

bregma 2y ago
Well, we use Linux dev machines but IT has loaded them up with enough panopticon software that several times a week for an hour or so I can not get enough CPU or resident RAM to do productive work. But at least there are no forced system reboots at inconvenient times during the work day.
- MathMonkeyMan 2y ago
  At a previous job they offered Linux laptops (yay!), but... - umask was not 022, so installing pretty much anything with `sudo make install` would fail, as would some software. - Running nmap caused an alert to phone home to IT, who would nag me on slack. - Opening well-known ports to my LAN (like 22) caused an alert to IT. - An "agent" program ran constantly, often using 100% of a CPU. The system overall had about 45 minutes of battery life. - Various system settings were overridden by a sysctl.d/ file that was regenerated by the agent at boot. Fortunately I know how ASCII sorting works and could produce a file that overrode the overrides. - Various capabilities (CAP_...) were disabled for my sudoer user. It wasn't that bad, and IT was helpful, but it was a persistent annoyance. Maybe what happened is somebody googled "how to harden Linux" and then just made everything on the first page of results company policy.
  - DmitryOlshansky 2y ago
    At my work they would also disable ptrace in the kernel and require you to explain why need it