Unrepentant Techno-Hermit, forever trying to make less do more.

  • 0 Posts
  • 65 Comments
Joined 3 months ago
cake
Cake day: March 8th, 2025

help-circle









  • Sorry for taking so long to get back to you on this, but I’m not always on Lemmy. There’s always more code to be written - you know how it is, I’m sure.

    Given the constraints you outline, one other avenue of attack could be to consider the time-sensitivity of product updates and the relative priority thereof. If it’s acceptable for updates to products to lag somewhat, you can at least perform them at a lower rate over longer time, thus reducing hardware load at any given time. If the periodic updates are make to the same per-product values, you could even potentially get smart and replace queued updates not yet performed, if they’re superseded by a subsequent change before they’re actually committed thus further reducing load.





  • Paying a premium for ridding yourself of institutional knowledge and existing experience, then paying again to fill the gap with ignorant novices, then paying yet again to train them to former levels of productivity while paying for the difference in the interrim: That’s government efficiency, baby!

    I mean, why pay for one thing once, when paying for the thing you already had before you threw it out four times over is clearly four times as good - just like how a double standard is twice as good as a boring singular standard. As Big Balls from DOGE would no doubt say: “That’s math”.