Niraj Bajaj
nirajbajaj.dev
Niraj Bajaj
@nirajbajaj.dev
::explorer
This is so cool. Appreciate your efforts!
January 6, 2026 at 3:49 PM
What made this special wasn’t the code, but realizing I reached for this instinctively and correctly.

That’s what good teaching does. Thank you Kyle Simpson.
(5/5)
January 6, 2026 at 3:45 PM
Here was my solution:
Array.prototype.last = function () {
if (this.length === 0) return -1;
return this[this.length - 1];
};
(4/5)

#JavaScript #DSA #LeetCode
January 6, 2026 at 3:45 PM
That intuition didn’t come from nowhere.

It came directly from reading You Don’t Know JS Yet: this & Object Prototypes by Kyle Simpson.
(3/5)
January 6, 2026 at 3:45 PM
The task was to add a last() method to Array.prototype.

My immediate intuition was to use this, because the method is reused and invoked at the call site. Runtime-bound, call-site-dependent behavior fits perfectly here.
(2/5)
January 6, 2026 at 3:45 PM
Big thanks to Per Borgen for the course 🙌
Next up: The Frontend Developer Path. Excited to see what’s coming!
(5/5)

#WebDevelopment #Frontend #HTML #CSS #LearningInPublic #BuildInPublic
December 29, 2025 at 5:56 PM
Also learned how GitHub and Netlify work together to deploy projects. Feels great to put your work out into the real world.
(4/5)
December 29, 2025 at 5:56 PM
Loved Scrimba’s interactive, project-based approach. Built things like a digital business card, a hometown landing page, and a studio landing page.
(3/5)
December 29, 2025 at 5:56 PM
HTML and basic CSS felt pretty smooth at first, but Flexbox definitely needed practice. Challenging, but in a good way.
(2/5)
December 29, 2025 at 5:56 PM
Big takeaway: the right mix of learning resources can make all the difference when learning to code.

What books or resources helped you most when learning JavaScript?

(8/8)

#JavaScript #LearningInPublic #WebDev
December 21, 2025 at 1:13 PM
Together, they’ve made my JavaScript learning process clearer, deeper, and more enjoyable.
(7/8)
December 21, 2025 at 1:13 PM
When I later moved to Eloquent JavaScript, something clicked. Kyle Simpson’s technical depth + Marijn Haverbeke’s explanations and analogies complement each other incredibly well.
(6/8)
December 21, 2025 at 1:13 PM
That combination helped solidify fundamentals and made the advanced concepts in YDKJS much more approachable.
(5/8)
December 21, 2025 at 1:13 PM
To properly absorb that depth, I needed help building the right mental models, so I paired it with JavaScript All-in-One For Dummies (Chris Minnick).
(4/8)
December 21, 2025 at 1:13 PM
I began with YDKJS and quickly realized how deep its conceptual and technical explanations go. Powerful but demanding.
(3/8)
December 21, 2025 at 1:13 PM
After some research, I chose You Don’t Know JS (Kyle Simpson) and Eloquent JavaScript (Marijn Haverbeke).
(2/8)
December 21, 2025 at 1:13 PM
let soonDataBase = ["MySQL", "MongoDB"];

console.log("Database: " + soonDataBase[0]);

for (let i = 1; i < soonDataBase.length; i++)
{
console.log(" " + soonDataBase[i]);
}

(4/n)
November 13, 2025 at 6:35 PM
let soonBackEnd = ["Node.js", "PHP"];

console.log("Back End: " + soonBackEnd[0]);

for (let i = 1; i < soonBackEnd.length; i++)
{
console.log(" " + soonBackEnd[i]);
}

console.log("");

(3/n)
November 13, 2025 at 6:35 PM
let frontEnd = ["HTML", "CSS", "JavaScript", "React"];

console.log("Front End: " + frontEnd[0]);

for (let i = 1; i < frontEnd.length; i++)
{
console.log(" " + frontEnd[i]);
}

console.log("");

(2/n)
November 13, 2025 at 6:35 PM