3 ms·
> It's ridiculously inefficient. You mean that simple tasks take many billable hours? Hmmm ...
by B1FF_PSUVM 5y ago
> It's ridiculously inefficient.
You mean that simple tasks take many billable hours?
Hmmm ...
- EvanAnderson 5y agoIrresponsible use of disk space, CPU cycles, and network bandwidth is more what I'm referring to. I've scripted some cleanup of profiles to take care of disk space exhaustion in a couple of situations. Cleaning up after Teams hasn't been a revenue generator for me, but it has created complaints. Anything that causes me to receive complaints from users draws my ire. (I subscribe to the "sewer system" theory of sysadmin for end-user facing servers, desktops, etc. You never think about your municipal sewer system unless it has problems. Ideally that's never. User-facing IT infrastructure should be the same.)
- B1FF_PSUVM 5y agoJust for kicks, a little gedanken-experiment: Product A costs 2 bazillion, and is perfect - for a 10 year lifetime, it works perfectly and requires no support. Zero additional cost. Product B does about the same, costs only 1 bazillion, but is rather shoddy - over a 10 year lifetime, it will require a further 3 bazillion worth of fixes, support and extra resources. That does feed a lot of families, though. Take your guess at what happens. Yeah, me neither.
- EvanAnderson 5y agoI feel like fractional reserve banking and the broken windows fallacy fit in here somewhere too. >smile<