11
Why frontend-heavy engineers need backend contract discipline
Notes on moving deeper into backend work by treating APIs, validation, schema design, and failure states as product contracts.
Writing
Notes archive
Older practical notes, retrospectives, and clear explanations from project work.
12
Why "full-stack" is only useful when the product path is clear
A practical framing of moving from frontend depth into full-stack product engineering without pretending every layer has equal depth.
13
Why a 1500+ article migration needed a workflow, not just Puppeteer
Notes from turning a large WordPress migration into a resumable Node.js automation pipeline with logs, checkpoints, and browser boundaries.
14
Why state-heavy interfaces fail without named events
Practical lessons from Angular and NgRx on making product behavior visible through actions, reducers, selectors, and predictable UI states.
/ Topics