There are all these subtle contracts in traditional backend engineering: a cache needs to be invalidated when some distant code changes, and that relationship is not formalized in the code itself. In @convex, you never have to manage caches or worry about consistency, because it's built into the architecture. It's kind of the ultimate pit of success for distributed systems.