3 ms·
While I agree with you in isolation, the context for that line is: > but it’s important to figure out what is truly necessary storage-wise versus what can be d
by DavidPiper 2y ago
While I agree with you in isolation, the context for that line is:
> but it’s important to figure out what is truly necessary storage-wise versus what can be derived on-the-fly. In the “v1” of something, I’ve found that minimizing as much mutable state as possible gets you pretty far.
It seems like the author is specifically calling out that you shouldn't store derived data unless you either can't recreate it easily or have measured (usually a post-v1 activity) that it is faster to store/cache that derived data.
- osigurdson 2y agoI think the author is always creating a certain type of application where db -> web server -> web page latency and throughput don't cause any performance problems. My main point is, don't assume that all applications are the same. Know when you are in new territory and the old heuristics don't apply. I'm triggered by context free "I usually find that..." and "In my experience..." assertions.