Ishwar Chandra Tiwari | codewithishwar

@codewithishwar

Bangalore, IndiaJoined March 2026

About

CodeWithIshwar - sharing insights on software engineering, DSA, system design, debugging, and practical development lessons. Created by Ishwar Chandra Tiwari.

Available for

Nothing here yet.

Ishwar Chandra Tiwari | codewithishwar's blogs

Most Engineers Debug the Code. Great Engineers Debug the Thinking.codewithishwar.hashnode.dev19 posts

Articles Threads Comments

Recently published

ICIshwar Chandra Tiwari | codewithishwarcodewithishwar.hashnode.dev

0

Why Mercurial Still Matters in 2026

1d ago · 2 min read · Most developers today know Git.But before Git became the industry standard, another distributed version control system was competing head-to-head with it: Mercurial (Hg) Interestingly, companies like

Join discussion

ICIshwar Chandra Tiwari | codewithishwarcodewithishwar.hashnode.dev

0

setTimeout() is not actually part of JavaScript 🤯

6d ago · 1 min read · Even in Node.js. When you write: setTimeout(() => { console.log("Hello"); }, 2000); the timer is NOT handled by JavaScript itself. In browsers: Timers come from Web APIs implemented in C++ In Nod

Join discussion

ICIshwar Chandra Tiwari | codewithishwarcodewithishwar.hashnode.dev

0

🚀 JavaScript Internals Most Developers Ignore

Apr 29 · 2 min read · Most developers think they know JavaScript. They don’t. They know syntax…but miss the real power behind it. ⚡ JavaScript isn’t powerful because of features It’s powerful because of how it behaves und

Join discussion

ICIshwar Chandra Tiwari | codewithishwarcodewithishwar.hashnode.dev

0

# ⚠️ Why a Simple Integer Breaks in Concurrency (Race Condition Explained)

Apr 27 · 3 min read · Even a simple shared integer can lead to unpredictable results in concurrent systems. 🧠 The Problem While working with concurrency, I came across something surprising. Consider this: One thread in

Join discussion

ICIshwar Chandra Tiwari | codewithishwarcodewithishwar.hashnode.dev

0

🧠 Memory: The Most Overlooked Bottleneck in Backend Systems

Apr 20 · 2 min read · When a system slows down, most developers look at CPU usage or blame inefficient code. But in many real-world cases, the actual issue is memory mismanagement. 🚨 Why Memory Becomes a Problem Memory i

Join discussion

Ishwar Chandra Tiwari | codewithishwar

About

Available for

Ishwar Chandra Tiwari | codewithishwar's blogs

Recently published

Why Mercurial Still Matters in 2026

setTimeout() is not actually part of JavaScript 🤯

🚀 JavaScript Internals Most Developers Ignore

# ⚠️ Why a Simple Integer Breaks in Concurrency (Race Condition Explained)

🧠 Memory: The Most Overlooked Bottleneck in Backend Systems

Search Hashnode

Ishwar Chandra Tiwari | codewithishwar

About

Available for

Ishwar Chandra Tiwari | codewithishwar's blogs

Recently published

Why Mercurial Still Matters in 2026

setTimeout() is not actually part of JavaScript 🤯

🚀 JavaScript Internals Most Developers Ignore

# ⚠️ Why a Simple Integer Breaks in Concurrency (Race Condition Explained)

🧠 Memory: The Most Overlooked Bottleneck in Backend Systems