
June 14th, 2026
Why I Standardize Every Node.js Project on UTC Time
A production engineering story about standardizing Node.js applications on UTC to prevent timezone bugs, offset errors, and cron failures.
10 min read
Blog · Author

@parveenkumar
Email team@parveenkumar.info
I build and ship web products, chase production bugs, and write down what actually worked—SEO, Next.js, performance, and the messy middle between “it works on my machine” and a calm dashboard.
Filter all posts by this author on the home feed.

June 14th, 2026
A production engineering story about standardizing Node.js applications on UTC to prevent timezone bugs, offset errors, and cron failures.
10 min read

June 7th, 2026
A production engineering story about separating background workers from the API, and the unexpected deployment challenges that arose.
12 min read

May 31st, 2026
A production engineering story about handling Node.js deployments safely using graceful shutdown, SIGTERM, and PM2 reload mechanisms.
11 min read

May 21st, 2026
Wi-Fi hid async bugs in my Next.js app. Chrome throttling exposed race conditions, stale UI, and wrong request order before users noticed.
17 min read

May 19th, 2026
Stale API responses overwrote fresh UI during fast navigation. AbortController and SWR fixed ghost requests in Next.js App Router.
15 min read

May 17th, 2026
App Router pushed me from Axios to native fetch: caching, AbortController, and fewer layers in production—not a package comparison rant.
14 min read