Efficiency is the enemy? (2021)
71–73 of 73 posts
Re: Efficiency is the enemy? (2021)
#72Oh, hello, queue theory and parallel processing theory! As you increase utilization (remove slack), throughput may grow, but latency grows more. If your nodes interact and depend on each other, the tail latency can grow completely out of hand, in exchange to tiny gains in utilization, and the actual throughput may go down as utilization goes up past some point. Always have some free disk space. Do not run your web se…
I think he'd probably be against "Max efficiency" thinking, but "Max effectiveness" thinking is still not the same as "Minimum major trouble". He's a bit too "Move fast and break things", which is kind of like max efficiency, if you define efficiency as "How much business growth can I pack in ten years".
I've always thought that things should be planned with "Time firebreaks", that are absolutely excluded from all ahead of time planning whatsoever, with the intent of cleaning up any unexpected trouble you run into. Not quite a break time, those are planned ahead and known to be necessary.
Re: Efficiency is the enemy? (2021)
#73Earlier quoted context omitted.
Assuming salary maps to value add, let's say if the CEO is worth 300x the secretary, he needs 300 secretaries.
I'm not sure if this comment was meant tongue-in-cheek, but wouldn't this assume the administrative overhead scales on a linear 1:1 ratio with the CEO's value? If a engineer's value is 2x another's, it doesn't necessarily mean the former uses, say, 2x the electricity/copier machine/office space. But maybe that was your point and I'm being dense.