No, the difference is lossless compression algorithms have a defined lower bound on how packed the bits can get. No such lower bound has been asserted here in terms of compressing your work, just the idea that you can drop 24 hours off the end of the week with no loss of productivity. Clearly 24 hours is arbitrary, why isn't Thursday a half day?
A more sound argument would be one with actual data and measurements about how reducing the workweek affected overall productivity of the team. Without that it's just opinions and guessing.
>No such lower bound has been asserted here in terms of compressing your work, just the idea that you can drop 24 hours off the end of the week with no loss of productivity. Clearly 24 hours is arbitrary, why isn't Thursday a half day?
No such lower bound is defined, but one need not be. The OP is merely stating that the lower bound is 32 hours or less. He's not dropping 24 hours off, merely 8 (or 9, that par is unclear).
As another commentor points out, the lower bound on compression algorithms varies by input. This is likely true here, too.
A more sound argument would be one with actual data and measurements about how reducing the workweek affected overall productivity of the team. Without that it's just opinions and guessing.