We waste so many resources customizing each response to time and observer and it’s just nuts. Most people aren’t going to notice if a calculation is being debounced, amortizing it over hundreds of seconds or requests. Instant gratification is the most expensive thing by far. And debouncing has such a profound effect similar to load shedding for traffic bursts, it really should be front and center in the literature.
When I was young I worked on a project that was so inefficient that I was professionally embarrassed to have my name associated with it. So I moved heaven and earth to fix it. Gave myself an RSI before I learned to better automate some transformations.
Today I’m also working on another, lesser embarrassment, but I’m not working weekends and holidays on it anymore. I’m not a hero surrounded by villains, I’m an observant person drowning in a sea of apathetic faces.
The amount of hardware we have per user request should have gotten someone fired. Most of the people responsible are gone, but one is still here complecting anything that isn’t nailed down, and few others know enough to realize that the reason they don’t feel confident in the code is because someone intentionally made it that way, and you should not be looking up to those people. They are literally making you dumber.