http://acko.net/blog/software-development-as-advanced-damage-control/

When you look at code from a data-centric view, a lot of things start to look like stale or inconsistent data problems. I don't like using the word "cache" for this because it focuses on the negative, the absence of fresh input. The real issue is data dependencies, which are connections that must be maintained in order to present a cohesive view and cohesive behavior, derived from a changing input model.

dude’s entire blog is full of gems

Can confirm.

The key to end-user happiness is to make tools that enable an equivalent level of affordance and flexibility compared to what the developer needed while developing it.

Most of all, we need the ambition to build complete tools and the humility to grant our users access on an equal footing, instead of hoarding the goods.

So much good stuff in there.

This issue was the driving force behind my earlier question about reactive calculations. I think most of the woes of state management and UI programming are for want of a good algorithm... (but also, most devs don't have a drive to build good foundations that make it easier to write the higher-level program.) https://futureofcoding.slack.com/archives/C5T9GPWFL/p1588994003263900