Learning a new framework in 48 hours

Deadlines don't care that you've never touched the framework. Here's the method I use to get productive in a new one inside two days — it's worked for every stack I've had to learn on the clock.

Hour 0–2: find what you already know

New frameworks are old concepts wearing new names. Component = function that returns UI. Router = URL to handler mapping. ORM = query builder with opinions. I write down the ten concepts I know exist in every web framework, then find each one's local name in the docs. After that, the documentation reads like a dictionary I mostly own.

Hour 2–6: the official tutorial, dishonestly

I do the tutorial, but with one rule: predict every line before running it. Where I'm right, I skip ahead. Where I'm wrong, that's the actual lesson. Tutorials are more useful as answer keys than as tours.

Hour 6–20: build the smallest real thing

Not a todo app — a sliver of the actual project. Real data, one real flow, deployed. The real project will drag me into auth, forms, errors, and deployment whether I like it or not; better to meet them early.

Hour 20–48: read one good codebase

I find a well-regarded open-source app in that framework and read it like literature. Idioms I'd never invent appear in the first hour.

The hidden ingredient is permission to be bad at it for one day. The deadline supplies the rest.