Ssandeepbansod007instackdevlife.hashnode.dev·May 1 · 9 min readRate Limiting Isn't Optional Here How to Actually Implement It in Node.jsIf your API has no rate limiting, any client can send as many requests as it wants. A broken retry loop, a scraper, or a user who refreshes too fast all of it hits your server with no limit. This guid00
Ssandeepbansod007instackdevlife.hashnode.dev·Apr 17 · 3 min readWe Deployed a "Small Fix" and Took Down Production — Here's What Actually HappenedA minor backend change caused a production outage, high CPU usage, and API failures. Here's how it happened, what we missed, and how we fixed it. The Incident It started as a simple task. "Just add o00
Ssandeepbansod007instackdevlife.hashnode.dev·Apr 12 · 7 min readWe Ran git rebase on a Shared Branch and Lost Three Days of WorkIt was a Thursday afternoon. Developer 1 had been working on a feature for four days. Clean commits, good code, reviewed and approved. He was about to open the final PR when he ran one command. git re00
Ssandeepbansod007instackdevlife.hashnode.dev·Apr 8 · 8 min readESM vs CJS — Why Your import Still Breaks in 2026 and How to Finally Fix ItYou install a package. You import it the normal way. Node throws ERR_REQUIRE_ESM. You switch to require(). Now TypeScript complains. You add "type": "module" to package.json. Now half your other impor00
Ssandeepbansod007instackdevlife.hashnode.dev·Apr 6 · 12 min readStop using `any` — here's how to type your messy API responses correctlyYou cast the API response to any to stop TypeScript complaining. It worked. Now a field changed shape three months later and the bug is in production. Here's how to type messy API responses properly —00
