Frontend engineering
Solve React and Next.js problems, design accessible interfaces, and choose useful server and client boundaries.
Showing 1–12 of 20 articles
Make deployment checks catch errors your local build misses
Build deployment checks around configuration, runtime APIs, storage access, and public route behavior so a successful local compile is useful evidence.
Prevent draft content from leaking through public caches
Separate public and privileged article reads, validate preview access, and test cache isolation with alternating anonymous and editor requests.
Keep a sitemap current when publishing new articles
Connect sitemap generation to published records, meaningful modification dates, and cache invalidation so discovery reflects actual public routes.
Generate metadata from the actual content contract
Build article metadata from validated public fields, resolve canonical URLs consistently, and catch missing properties before a page quietly publishes defaults.
Return a real 404 instead of a not found message with status 200
Distinguish missing content from outages, invoke the route's missing-resource mechanism, and verify status codes before and after streaming begins.
Make a blog article available in its initial HTML
Move an article's public read into the server render and verify the actual document response, missing-resource behavior, and client enhancements.
Why fetching your own API from a server page can break deployment
Replace server-to-self HTTP calls with a shared data function after identifying build-time origins, forwarded credentials, and public endpoint boundaries.
Stop published content from staying stale after an edit
Trace an edited article through data, rendered-route, browser, and CDN caches so publishing has an explicit and testable freshness contract.
Diagnose hydration errors with a minimal failing page
Reduce a hydration warning to the first server and browser disagreement, then repair unstable dates, storage reads, or invalid markup at their source.
Choose a server or client component by following the data
Follow a product page's data from database to browser to choose a small client boundary without exposing secrets or moving every component.
Use AI to review frontend behavior beyond the screenshot
Review frontend work with AI using keyboard, network, state, recovery, and responsive evidence so a convincing screenshot does not hide broken user journeys.
Build a large table without freezing the browser
Keep large tables responsive by measuring data preparation and DOM work, then choosing bounded fetching, pagination, or virtualization with explicit interaction tradeoffs.
Explore topics
Subscribe to Newsletter
Get the latest articles and updates delivered to your inbox.