The Stack Changed While You Were Away
A no-nonsense map of what is new since you last wrote code — and what is safe to ignore.
[ cover screenshot ]
If you stepped away around the early 2010s, the surface area looks terrifying. It isn’t. Most of it is the same ideas wearing new names. Here’s the field guide I wish someone had handed me.
What actually changed
- The frontend got components. Whether it’s React, Svelte, or something newer, the unit of UI is now a function that returns markup. Learn that one idea and the framework wars stop mattering.
- Types came back. TypeScript is the default. Your instinct for what a function should accept and return is now enforced by the editor.
- Deploys got boring. Push to a branch, a URL appears. The weekend of server config is gone.
What’s safe to ignore (for now)
You do not need to learn Kubernetes to ship a side project. You do not need to pick the “right” state library before writing a line. You do not need to understand the entire build pipeline — the agent will scaffold it and you can learn it later, on purpose, when something breaks.
The fundamentals you already own — data modeling, debugging, knowing when something smells wrong — are worth more than any framework. Start building; the names sort themselves out.