NAYAN’S ENGINEERING JOURNAL
Notes worth keeping.
Page 6 of 9.
My collection of practical guides on React, Angular, JavaScript, frontend design, performance, technical SEO and reliable delivery. Explore a topic, follow an example, and check the details.
103 GUIDES IN THE JOURNAL / 12 ON THIS PAGE
Engineering articles
Manage File Preview URLs Without Memory Leaks
Create, replace and revoke object URLs at the right point in image preview and download workflows.
Model UI States with TypeScript Discriminated Unions
Replace conflicting booleans with explicit loading, success and error states that narrow safely.
Optional Chaining and Nullish Defaults Without Hidden Bugs
Keep zero, false and empty text meaningful while safely reading genuinely optional values.
Organize Angular Reactive Forms Around the Data Model
Make controls, validation rules and submission state explicit in editable Angular workflows.
Place Next.js Client Boundaries Around Interaction, Not Entire Pages
Keep content and metadata on the server side while giving stateful controls the browser capabilities they need.
Prepare a Static Website Rollback Before the Release Needs One
Retain complete artifacts and restore coherent document and asset versions instead of copying a few old files over a broken release.
Prevent Layout Shifts by Reserving the Space Your Content Will Need
Stabilize images, async messages, fonts and embeds so content does not move unexpectedly while someone reads or clicks.
Profile React Rendering Before Adding Memoization
Investigate slow interactions by measuring render work, state placement and browser cost separately.
Progressive Enhancement: Keep Content Useful Before JavaScript Runs
Build readable pages first, then layer on filtering, animation and richer interactions without making the content depend on them.
Promise Error Handling That Keeps Failures Visible
Design promise chains with clear ownership of errors, honest UI feedback and reliable cleanup.
Publish a Static Website with Separate GitHub Actions Build and Deploy Jobs
Use an uploaded build artifact, explicit Pages permissions and a deployment dependency that preserves what was tested.
React State vs Ref: Choose by What the Screen Must Show
Keep rendered information in state and operation handles in refs without hiding updates from the UI.
Put a useful idea to work.
Try the browser utilities in my developer toolkit.