CoderRitik Official

01/03/2026

JavaScript Event Loop Explained in 30 Seconds 🤯 | Promise vs setTimeout

🔥 Explanation (Minimal & Clear)

JavaScript is single-threaded → uses Event Loop.
Promise = Microtask
Runs before setTimeout.
Microtasks have higher priority.
setTimeout = Macrotask
Even with 0ms, it waits.
Goes to Task Queue.

Ex*****on order:
Run all synchronous code first.
Then run Microtasks (Promise).
Then run Macrotasks (setTimeout) in order added.

So:
promise runs first.
Then first timeout1
Then timeout2
Then last timeout1

22/02/2026

JavaScript Event Loop TRICK 😱 | Why Output is A D C B?

console.log → runs first (Synchronous).
Promise.then() → Microtask Queue (runs before setTimeout).
setTimeout() → Macrotask Queue (runs last)

,
loop
javascript,
javascript,
vs promise,
interview question,
tricky question,
developer,

development,
microtask queue,
queue,
reels,
learn javascript fast,
,
content

08/02/2026

JavaScript Async Await Trick 🤯 | Why Output Is A B D C ?

Ultra-Short Explanation (Key Points)

foo1() starts → prints A
foo2() is async → pauses at await
foo3() runs immediately → prints B
JS doesn’t wait → prints D
Promise resolves → prints C

👉 Final Output: A B D C

Async doesn’t mean blocking 😈 JavaScript fooled you again!

05/02/2026

This JavaScript Line Will Blow Your Mind 🤯 | typeof Trap

Can you guess the output? 👀
This one-liner uses assignment chaining + typeof in JavaScript and gives a result most developers don’t expect.
Perfect example of why JavaScript ex*****on order matters ⚠️

var z = 1, y = z = typeof y;
👉 typeof y runs before y exists
👉 typeof y → "undefined"
👉 z = "undefined"
👉 y = "undefined"

Watch till the end 💡
Save & share with your JS friends

01/02/2026

JavaScript Weird Parts 🤯 | Objects, Arrays & Type Coercion Explained

JavaScript doesn’t compare values here — it compares references and types


Array vs object

28/01/2026

JavaScript is Lying to You 😱 | true + false Explained

JavaScript behaves differently because of type coercion.
When you use operators like + or ==, JavaScript automatically converts values into numbers or compares only their values instead of types.

true is converted to 1
false is converted to 0

The + operator performs numeric addition when values are not strings

The == operator compares values after implicit type conversion

That’s why:
true + false becomes 1
false + false becomes 0
true + true becomes 2
'0' == false is true
false == 'false' is false

⚠️ This behavior often causes confusion and bugs in real projects and is commonly asked in JavaScript interviews.

Best practice:
Always use strict equality (===) to avoid unexpected results.

26/01/2026

JavaScript behaves differently with + and - operators.
This short explains type coercion, string conversion,
and the famous typeof null and typeof Array confusion.

A must-know JavaScript interview concept for web developers.

25/01/2026

Why does this JavaScript function return 5 instead of "xyz" or {}?

This happens because of the comma operator in JavaScript.
The comma operator evaluates each expression from left to right
and returns the value of the LAST expression.

This is a common JavaScript interview question and an advanced concept
every web developer should understand.

javascript comma operator
javascript return value
advanced javascript
javascript interview question
js tricky code

22/01/2026

JavaScript code comparing object references using strict equality with console output

20/01/2026

18/01/2026

18/01/2026

JavaScript Security Trap 😱 | Closures + eval() Explained