3 min read
Building a Data Import Wizard: Designing for the Messy Spreadsheet, Not the Clean Demo
Lessons from building a frontend data import wizard for real, messy spreadsheets — inconsistent headers, missing values, and mixed types.
Deep dives and honest takes from production work — JavaScript and TypeScript, frameworks, CSS and UI engineering. Color-coded by topic so you can follow the threads you care about.
36 posts
3 min read
Lessons from building a frontend data import wizard for real, messy spreadsheets — inconsistent headers, missing values, and mixed types.
3 min read
A practical guide to React state management in 2026 — when Context and Zustand are enough, and when Redux still earns its place.
3 min read
The TypeScript features that actually earn a spot in daily production code — template literal types, satisfies, const assertions, and utility types.
3 min read
What CSS container queries are, how they differ from media queries, and a practical example of a component that adapts to its own container.
3 min read
A step-by-step overview of turning a Next.js app into a Progressive Web App — manifest, service worker, and real-device testing.
3 min read
How to use Web Workers to run heavy JavaScript computation without freezing the main thread, with a file-processing example.
3 min read
What design tokens are and how they solve the classic 'the build doesn't match the design' problem, explained for developers and designers.
3 min read
Honest first impressions of Svelte from a developer with years of production experience in Angular, React, Vue, and Next.js.
3 min read
How discriminated unions in TypeScript let you safely handle multiple states — loading, success, error — without endless undefined checks.
3 min read
What separates a good dark mode implementation from an inverted-colors hack — CSS variables, system preference detection, and contrast checking.
3 min read
A genuinely useful answer to 'Angular or React in 2026' based on years of professional experience in both — because the honest answer depends on context.
3 min read
The four most common places JavaScript memory leaks hide — event listeners, intervals, closures, and detached DOM nodes — with fixes.