Blessing Computers
An internal admin dashboard and e-commerce storefront on Next.js 16 — and my most senior work to date: architecture guardrails that outlast any one developer, a failure-mode-first auth layer, and fixes for the platform edges nobody sees until they break.
A dashboard that had to be reliable — and stay that way as it grew.
The admin dashboard runs the business, so its failure modes matter more than its happy path. It needed auth that never logs people out mid-task, a data layer that fails predictably, and structure that stops a growing codebase from turning into a tangle of cross-imports. The interesting problems here were reliability and maintainability at a level that survives more than one developer.
Guardrails first, then build inside them.
Five pillars, each aimed at a way the system could quietly rot or fall over.
Module boundaries checked in CI with eslint-plugin-boundaries, barrel-only imports, ten documented ADRs, and a feature-scaffolding generator so every new feature starts on the rails.
A typed data layer with single-point API-envelope unwrapping and error normalization — every response is validated and every failure shaped the same way before it reaches a component.
Server-seeded sessions, no-retry token rotation, and a Web Locks cross-tab single-flight refresh — so any number of tabs coordinate one refresh instead of racing and logging each other out.
Fail-fast env isolation with strict client/server separation, IP-block recovery plus a Vercel WAF + bot-protection spec, and a production cookie-forwarding fix that restored authenticated requests behind the edge.
A serverless upload proxy to sidestep Vercel edge timeouts on large files, and an AI smart-paste parser built behind a testable LLM seam so the model can be swapped or mocked.
The e-commerce storefront runs on a custom Next.js server with database-backed API routes, typed product and blog models, and a contact-agent feature.
A codebase that fails predictably and grows cleanly.
Cross-tab logout races are gone, responses and errors flow through one typed path, and CI blocks the imports that would erode the architecture. It shipped with documented ADRs, migration guides, and consistently green tsc / eslint / build pipelines — the kind of foundation a second and third engineer can build on without a handover doc.
