New posts
1/mo
New flagship post to publish each month.
Roadmap refreshed on April 8, 2026. The goal is simple: publish one substantial post each month, refresh one older evergreen guide, and keep related topics tied together through series instead of scattered one-offs.
New posts
1/mo
New flagship post to publish each month.
Refreshes
1/mo
Older article to refresh every month so the archive stays current.
Series
3
Active tracks grouping related writing into clear editorial threads.
One flagship post each month, plus one refresh to an older evergreen article so the archive keeps compounding instead of aging in place.
Search intent: ai coding delivery process engineering
Evergreen refresh
Continuous Integration and Deployment for Next.js Projects
Search intent: playwright accessibility testing workflow
Evergreen refresh
Testing React Components with Vitest and React Testing Library
Search intent: developer experience metrics for engineering teams
Evergreen refresh
Development Workflow with Husky for Next.js, ESLint, and Vitest Integration
Search intent: eslint package architecture for teams
Evergreen refresh
Migrate ESLint 8 or Less to ESLint 9
Search intent: astro alpine performance patterns
Evergreen refresh
Storybook in Action with Next.js, Tailwind and TypeScript
Search intent: architecture notes for developer seo
Evergreen refresh
Atomic Module Component Structure for React
These are the active tracks already live on the site, grouped so readers can move through a topic in order instead of guessing what comes next.
A practical sequence for turning a fresh Next.js codebase into a product teams can lint, test, document, deploy, and secure with confidence.
A guided walkthrough from project structure to auth and delivery.
Browse seriesA focused track on config design, migrations, and the standards work that keeps code reviews sharper without slowing teams down.
Evergreen tooling notes for teams standardizing JavaScript and TypeScript work.
Browse seriesA running set of principles on ownership, review quality, code clarity, responsive thinking, and releases that do not rely on heroics.
Opinionated field notes on how strong software teams stay clear, calm, and accountable.
Browse series