Lessons in thinking like a frontend engineer.https://front-in-the-end.pages.dev/https://front-in-the-end.pages.dev/lessons/async/network-is-part-of-your-ui/https://front-in-the-end.pages.dev/lessons/async/network-is-part-of-your-ui/Every fetch puts your interface into one of four states, whether you designed them or not. The ones you didn't design are the ones your users meet at the worst time.https://front-in-the-end.pages.dev/lessons/rendering/the-document-is-enough/https://front-in-the-end.pages.dev/lessons/rendering/the-document-is-enough/Every frontend architecture is a workaround for something documents couldn't do. Know what documents can do, or you'll pay for workarounds you didn't need.https://front-in-the-end.pages.dev/lessons/state/state-vs-derived/https://front-in-the-end.pages.dev/lessons/state/state-vs-derived/Most of what we call state is a derivation wearing state's clothes. Every derivable value you store is a synchronization job you just hired yourself for.https://front-in-the-end.pages.dev/lessons/thinking/the-platform-beneath/https://front-in-the-end.pages.dev/lessons/thinking/the-platform-beneath/A framework is an opinion about the platform, not a replacement for it. Build the 20-line version once and every framework you ever meet becomes legible.https://front-in-the-end.pages.dev/lessons/async/race-conditions/https://front-in-the-end.pages.dev/lessons/async/race-conditions/The network reorders your responses and your UI applies them as they arrive. The fix is one rule — never trust arrival order — and one integer that enforces it.https://front-in-the-end.pages.dev/lessons/rendering/enhancement-vs-takeover/https://front-in-the-end.pages.dev/lessons/rendering/enhancement-vs-takeover/The dividing line isn't how much JavaScript you write — it's who owns the DOM. Cross from enhancing to owning deliberately, because you can't easily cross back.https://front-in-the-end.pages.dev/lessons/state/single-source-of-truth/https://front-in-the-end.pages.dev/lessons/state/single-source-of-truth/Every copy of a fact is a future disagreement. The fix isn't better synchronization — it's making disagreement structurally impossible.https://front-in-the-end.pages.dev/lessons/thinking/logic-outlives-views/https://front-in-the-end.pages.dev/lessons/thinking/logic-outlives-views/The code your framework never touches is the code the rewrite never breaks. Keep the rules of your product in plain modules, and let components be the thin layer that wires them to pixels.https://front-in-the-end.pages.dev/lessons/async/cancellation-and-debounce/https://front-in-the-end.pages.dev/lessons/async/cancellation-and-debounce/The race guard protects your UI but still pays for every request. Debounce stops doomed work before it starts; abort stops it mid-flight. Most real inputs want both.https://front-in-the-end.pages.dev/lessons/rendering/the-spa-bargain/https://front-in-the-end.pages.dev/lessons/rendering/the-spa-bargain/A single-page app trades the browser's free features for control. The trade is real and sometimes excellent — but the bill is itemized, and most teams never read it.https://front-in-the-end.pages.dev/lessons/state/where-state-lives/https://front-in-the-end.pages.dev/lessons/state/where-state-lives/Component state is the default, and the default is a choice. The placement ladder: as close as possible, as durable as required — and the URL is criminally underused.https://front-in-the-end.pages.dev/lessons/thinking/impossible-states/https://front-in-the-end.pages.dev/lessons/thinking/impossible-states/Clean frontend code isn't about line counts — it's about interfaces that can't express nonsense. Every boolean prop doubles your states; most of the new ones are garbage.https://front-in-the-end.pages.dev/lessons/async/optimistic-updates/https://front-in-the-end.pages.dev/lessons/async/optimistic-updates/Showing success before the server confirms is a lie with a budget — cheap when failure is rare and rollback is honest, ruinous when either condition fails. Know the conditions.https://front-in-the-end.pages.dev/lessons/rendering/ssr-and-hydration/https://front-in-the-end.pages.dev/lessons/rendering/ssr-and-hydration/Server-side rendering bolts the document's strengths back onto the SPA — at the price of rendering everything twice. Hydration isn't a feature; it's the bill for wanting both worlds.https://front-in-the-end.pages.dev/lessons/state/server-state-is-a-cache/https://front-in-the-end.pages.dev/lessons/state/server-state-is-a-cache/What your components hold is never the server's truth — it's a snapshot, aging since the moment it arrived. Treat it as a cache, because that's what it is whether you admit it or not.https://front-in-the-end.pages.dev/lessons/thinking/web-components/https://front-in-the-end.pages.dev/lessons/thinking/web-components/The platform grew its own component system while everyone was watching frameworks. It's not a framework replacement — it's the interop layer, and knowing where it wins is the skill.https://front-in-the-end.pages.dev/lessons/async/honest-failure/https://front-in-the-end.pages.dev/lessons/async/honest-failure/The deepest async bug isn't an error — it's not knowing whether the thing happened. Design for ambiguity with safe retries, and the impatient user stops being dangerous.https://front-in-the-end.pages.dev/lessons/rendering/choosing-a-rendering-strategy/https://front-in-the-end.pages.dev/lessons/rendering/choosing-a-rendering-strategy/Content or app, stranger or regular, short session or long — three questions decide the rendering strategy. Fashion decides it more often, and that's why this lesson exists.https://front-in-the-end.pages.dev/lessons/state/designing-state/https://front-in-the-end.pages.dev/lessons/state/designing-state/State design is four questions asked per fact — is it state, who owns it, where does it live, is it ours or a snapshot. Run the drill until it's boring; boring is the goal.https://front-in-the-end.pages.dev/lessons/thinking/surviving-churn/https://front-in-the-end.pages.dev/lessons/thinking/surviving-churn/Frontend knowledge has a half-life, and pretending otherwise is how careers stall. Sort your learning into what compounds and what depreciates — then read every new tool's price tag the same way.