JavaScript’s this keyword is one of the most misunderstood parts of the language — not because it’s complex, but because it’s often explained without context. When I first learned it, this felt unpredictable. Sometimes it worked. Sometimes it didn’t. And most explanations felt like rules to memorize, not ideas to understand. What helped me wasn’t another syntax breakdown — it was changing how I thought about the problem. I started looking at this through a lens I didn’t expect to use while coding: philosophy. In this video, I explore: why this depends on how a function is called why context in JavaScript is closer to action and ownership than to variables and how ideas from René Descartes helped the concept finally click for me This isn’t a “trick” video. It’s an attempt to explain why JavaScript behaves the way it does, not just how to use it. I’m continuing this series by connecting JavaScript fundamentals to how humans reason about identity, context, and change. If you enjoy learning concepts deeply — instead of memorizing patterns — you might find this perspective interesting. I’d love to hear how you approach learning or teaching difficult technical ideas. #JavaScript #SoftwareEngineering #FullStackDevelopment #LearningInPublic #DeveloperMindset #TechnicalLeadership #ProgrammingConcepts

To view or add a comment, sign in

Explore content categories