Learning the backend on a frontend engineer's clock
Not a detour — a deliberate move into schemas, APIs, and the half of the system I used to treat as a black box.
Draft outline — replace with the real story.
For a while, "the backend" was the thing my code talked to and I never had to think about. This is how I stopped treating it as a black box — on the nights and weekends a frontend job leaves you.
The wall I kept hitting
The moment the frontend-only view stopped being enough. A feature you couldn't build, a bug you couldn't trace past the network tab.
Where I started
Be concrete: the first API you owned, the first schema you designed. Express, Sequelize, MySQL — what clicked and what didn't.
What frontend taught me about backend (and vice versa)
The transferable instincts — naming, contracts, thinking in failure states — and the ones you had to unlearn.
Where it left me
T-shaped, not scattered. Why the range made you a better engineer on both sides of the request.