The context window is not memory. Three habits I use to work with the constraint instead of against it — and why each is just structured omission in disguise.
You do not need C4 diagrams to think in systems. A well-named function and a clear data model are already system thinking — diagrams are communication tools, not thinking tools.
Why React Server Components feel awkward at first but click into place once you stop fighting the grain of the model — server by default, client only when you need browser APIs.
How I finally internalised edge functions: not 'servers closer to users' but 'logic that moves to where the data lives.' A data-locality optimisation, not a deployment topology.
Most token systems break down at scale. Three patterns that keep them coherent across hundreds of components: tiered naming, single-team ownership, and build-time enforcement.
