Working notes on React, performance, motion and the parts of frontend engineering that only get interesting once real money is involved. Written as markdown, rendered at build time.
Most React codebases do not fail because of React. They fail because of where the state lives, what owns the data fetching, and how the folder tree lies about the product.
A reconciliation table with a 90-day window, live status updates and analysts who scroll fast. Here is how we kept it interactive instead of turning it into a loading spinner.
Performance work fails for organisational reasons, not technical ones. A budget only survives if it is small, automatic and owned by a name.
I put off containers for a year because every tutorial started with a Go service. Here is the mental model that made it obvious, plus the multi-stage build I actually use.