Mastering JavaScript Strings & Dates

🚀 Day 10 of My JavaScript Journey ✨Today I explored how JavaScript actually works behind the scenes — and honestly, it changed the way I look at code completely 🤯 Here’s what I learned 👇 🧠 How JavaScript Code RunsJavaScript doesn’t just execute line by line — it first creates an Execution Context which manages everything. ⚙️ Execution Context Phases1️⃣ Memory Allocation Phase Variables get stored with undefined Functions are stored completely 2️⃣ Execution Phase Code runs line by line Values get assigned and functions execute 📦 Call Stack & Execution Flow JavaScript uses a Call Stack to manage function calls Each function creates its own execution context Stack follows LIFO (Last In, First Out) 💾 Stack vs Heap Memory Stack → Stores primitive values (fast ⚡) Heap → Stores objects (reference-based 🧩) 🤖 Interpreter BehaviorJavaScript reads and executes code step by step using an interpreter — not compiled like some other languages. ❓ Why undefined Appears?Because during memory phase, variables are declared but not initialized yet. ⬆️ Hoisting Explained var is hoisted with undefined Functions are fully hoisted let & const are hoisted but stay in Temporal Dead Zone (TDZ) ❌ 🚫 Temporal Dead Zone (TDZ)You can’t access let & const variables before initialization — it throws an error. ⚠️ Function Expressions vs Hoisting Function declarations → hoisted ✅ Function expressions → behave like variables ❌ 💡 Key TakeawayUnderstanding execution context, memory, and hoisting makes debugging WAY easier and helps write cleaner code 🔥 📌 Slowly moving from writing code → to understanding how it actually works inside #JavaScript #WebDevelopment #MERNStack #CodingJourney #LearnToCode #FrontendDevelopment #DeveloperLife

🚀 Day 8 of My JavaScript Journey 👉Today was all about mastering Objects, Memory & Advanced Concepts — and honestly, this was one of the most powerful days so far 🔥 Here’s what I learned 👇 📌 Creating & Using Objects How to create objects and print them Access properties using dot notation & bracket notation Learned why keys are always strings 📌 CRUD Operations Create, Read, Update, Delete in objects 👉 Real-world data handling finally makes sense now! 📌 Dynamic Keys & Special Cases Bracket notation for dynamic keys Handling keys with spaces Using Symbols as keys 📌 Object Methods & this Keyword Adding functions inside objects Calling methods Understanding this and why it’s important 💡 📌 Loops & Iteration for...in loop for keys & values for...of with objects (via entries) Object.keys(), Object.values(), Object.entries() 📌 Destructuring Object destructuring Array destructuring Renaming variables while destructuring 📌 Copying Objects Copy by reference (important concept ⚠️) Shallow copy using spread operator ... Deep copy using structuredClone() 📌 Nested Objects Creating and accessing nested structures 👉 Feels like working with real APIs now! 📌 Arrays & Objects in Memory Arrays are actually objects 🤯 Reference behavior in arrays & objects Memory concepts: stack vs heap How pointers & references actually work internally 📌 Advanced Insights Object structure in memory Optimization techniques Why const arrays can still change (push works!) 💡 Key Takeaway: 👉Objects are the backbone of JavaScript. Understanding how they work in memory completely changes how you write code. 🔥 Day 8 complete — getting closer to thinking like a real developer! #JavaScript #WebDevelopment #CodingJourney #Day8 #LearnToCode #DeveloperLife

I’ve started learning scope in JavaScript, but before diving into it, I took an interesting detour into a very important question: Is JavaScript compiled or interpreted? Before getting into scope properly, I learned that JavaScript does not behave like a simple line-by-line interpreter. A good example is this: ```js console.log("Hello"); function foo() { console....log("world"); } console.log("hello world"); ``` If JavaScript was executed in a purely naive line-by-line way, we might expect "Hello" to be logged before the error appears. But that does not happen. The script fails before execution starts because the JavaScript engine first goes through an initial preparation phase. That phase includes things like: 1. parsing the code 2. checking whether the syntax is valid 3. building an internal representation 4. preparing the code for execution So a better mental model is: Source code -> Parse / syntax check -> Internal representation / compilation steps -> Execution This helped me understand that calling JS simply “interpreted” is not the full picture. Modern JavaScript engines like V8 are much more advanced. They can parse code, create internal representations, interpret some code, compile parts into bytecode or internal instructions, and even JIT-compile frequently used parts for better performance. So JavaScript is commonly called an interpreted language, but in modern engines, the reality is more nuanced. This also connects nicely with scope. Scope is about the visibility of variables and functions in code, but before JavaScript can execute code, the engine first needs to understand the structure of that code. That means scope is not just a runtime topic. It is closely connected to how the engine reads, parses, and prepares the program. My main takeaway: JavaScript is not random, and it is not just “reading one line at a time”. There is a preparation phase before execution, and understanding that makes topics like scope, hoisting, and errors much easier to reason about. #JavaScript #TypeScript #WebDevelopment #SoftwareEngineering #V8 #LearningInPublic

🚀 From Tricky to Clear — My JavaScript Practice Journey🚀 💡Today I worked on a couple of problems that initially felt tricky, but after breaking them down step by step, I was able to solve them completely. 💡 🔹 Problem 1: String to Object Conversion I learned how to transform a string into meaningful key-value pairs by grouping characters and mapping them into an object. 👉 This improved my understanding of: • String manipulation • Index-based iteration • How data can be structured dynamically 🔹 Problem 2: Rearranging Array (Positive & Negative) This problem was more challenging. I worked on separating positive and negative numbers and then merging them in a specific pattern. 👉 Key takeaways: • Logical thinking and pattern recognition • Handling multiple arrays efficiently • Using loops to control data flow step by step ✨ What I realized: At first, these problems looked confusing, but once I broke them into smaller parts, they became much easier to solve. Consistent practice is really helping me improve my problem-solving skills. #JavaScript #ProblemSolving #CodingJourney #FrontendDevelopment #LearningInPublic

Day 3: Hoisting — The JavaScript "Magic" That Isn't Magic at All! 🎩✨ Today, I tackled one of the most famous (and often misunderstood) concepts in JavaScript: Hoisting. If you've ever wondered why you can call a function before you even define it in your code, you've witnessed Hoisting in action! 🤔 What is Hoisting? Hoisting is a mechanism where variables and function declarations are moved to the top of their containing scope during the Memory Allocation Phase, before the code even starts executing. 🔍 Under the Hood (The Execution Context) Remember the "Big Box" (Execution Context) from Day 1? Here is what happens during the Memory Phase: Variables (var): JS allocates memory for variables and initializes them with a special value: undefined. Functions: JS stores the entire function body in memory. This is why: Calling a function at Line 1 works perfectly! ✅ Accessing a var at Line 1 returns undefined instead of an error! ⚠️ 💻 The Browser Demo (The Call Stack) Watching this live in the Sources tab of Chrome DevTools was a game-changer. Seeing the Global scope populate with variables before the first line of code executed made everything click. 💡 Interview Tip: When asked "What is Hoisting?", don't just say "it moves code to the top." Better Answer: "Hoisting is the process where the JS Engine allocates memory for variables and functions during the Creation Phase of the Execution Context. This allows us to access functions and variables even before they are initialized in the code, though var will return undefined until the execution reaches its assignment." Next up: Diving into how let and const handle hoisting differently (The Temporal Dead Zone!). Are you a var, let, or const person? Let's discuss below! 👇 #JavaScript #WebDevelopment #Hoisting #NamasteJavaScript #CodingInterviews #FrontendEngineer #ProgrammingLogic #JSFundamentals

Day 6 of My JavaScript Journey 🚀 Today, I learned some important JavaScript concepts: • Truthy and Falsy values • Equality operators • Boolean logic (logical operators) Truthy values are values that evaluate to true, while falsy values (like 0, "", null, undefined, NaN) evaluate to false in conditions. I also learned about equality operators: • Loose equality (==): compares values but converts types • Strict equality (===): compares both value and type For example: 5 == "5" → true 5 === "5" → false I also explored logical operators: • && (AND) • || (OR) • ! (NOT) One key thing I learned: Using strict equality (===) helps avoid unexpected bugs caused by type conversion. Bonus: I was given a challenge on these concepts and I successfully completed it. Key takeaway: Understanding how JavaScript evaluates conditions is crucial for writing reliable code. #JavaScript #WebDevelopment #LearningInPublic #100DaysOfCode

🚀 Day 7 — Understanding JavaScript Objects & Prototypes Continuing my journey of strengthening core JavaScript fundamentals, today I explored one of the most important building blocks — Objects & Prototypes 👇 At first, objects feel simple… but when you dive into prototypes, you truly understand how JavaScript works behind the scenes. 🔹 Covered topics: - What are JavaScript Objects? - Key-Value Pairs & Properties - Dot vs Bracket Notation - Add / Modify / Delete Properties - Object Methods - "this" inside objects (quick revision 🔁) - Constructor Functions - What happens when we use "new" - Why Prototype is needed (memory optimization 🔥) - Prototype & Shared Methods - Prototype Chain (🔥 very important) - Getter & Setter 💡 Key Learning: JavaScript is not class-based — it’s prototype-based. Objects can share properties and methods using prototypes, which makes code more efficient and scalable. 👉 Always remember: - JS first looks inside the object - If not found → it checks the prototype (This is called the Prototype Chain) Understanding this concept is a game changer for interviews and helps in writing better, optimized code. 📌 Day 7 of consistent preparation — going deeper into JavaScript fundamentals 🔥 #JavaScript #WebDevelopment #FullStackDeveloper #CodingJourney #MERNStack #InterviewPreparation #Frontend #Backend #LearnInPublic #Developers #Consistency #100DaysOfCode #LinkedIn #Connections

Day 17 of my JavaScript learning journey 🚀 Today, I started building a Form Validation system using HTML, CSS, and JavaScript. This one felt different from my previous projects because it’s closer to real-world applications, every website needs proper form validation. Here’s what I worked on: • Validating user input fields (Name, Phone, Email, Message) • Displaying real-time error messages • Using regex to check for correct name format • Preventing empty submissions • Giving visual feedback (error text & success icons) • Structuring cleaner validation functions One thing I learned today is how important user experience is. It’s not just about collecting input, it’s about guiding the user and preventing mistakes before submission. I also started understanding how to break logic into small functions like: • validateName() • validateEmail() • validatePhone() That made the code easier to manage and debug. Still working on improving validation for all fields, but this is a solid step forward. Consistency is paying off 💪 #JavaScript #WebDevelopment #Frontend #100DaysOfCode #LearningInPublic

🚀 Understanding the JavaScript Event Loop (Simple Explanation) Ever wondered how JavaScript handles multiple tasks even though it’s single-threaded? 🤔 That’s where the Event Loop comes in! 👉 In simple terms: The Event Loop manages execution of code, handles async operations, and keeps your app running smoothly. 🔹 Key Components: Call Stack → Executes functions (one at a time) Web APIs → Handles async tasks (setTimeout, fetch, etc.) Callback Queue → Stores callbacks from async tasks Microtask Queue → Stores Promises (higher priority) Event Loop → Moves tasks to the Call Stack when it's free 🔹 Example: console.log("Start"); setTimeout(() => { console.log("Timeout"); }, 0); Promise.resolve().then(() => { console.log("Promise"); }); console.log("End"); 👉 Output: Start End Promise Timeout 🔹 Why this output? "Start" → runs first (Call Stack) "End" → runs next Promise → goes to Microtask Queue (runs before callbacks) setTimeout → goes to Callback Queue (runs last) 💡 Key Insight: 👉 Microtasks (Promises) always execute before Macrotasks (setTimeout) 🔥 Mastering the Event Loop helps you write better async code and avoid unexpected bugs! #JavaScript #Frontend #WebDevelopment #Coding #InterviewPrep

🚀 Day 8 — Mastering JavaScript Arrays & Higher Order Functions Continuing my journey of strengthening core JavaScript fundamentals, today I focused on one of the most practical and frequently used concepts — Arrays & Higher Order Functions 👇 Arrays may look simple at first, but when combined with higher order functions like "map", "filter", and "reduce", they become extremely powerful for solving real-world problems. 🔹 Covered topics: - What are Arrays & why we use them - Indexing & accessing elements - Adding & removing elements ("push", "unshift", "splice") - Difference between "slice" & "splice" - Common methods ("indexOf", "includes", "sort") - Higher Order Functions (🔥 important) - "forEach()" vs "map()" - "filter()" for conditional data - "reduce()" for complex logic (🔥 most important) - "find()" & "findIndex()" - Method chaining (real-world usage 💡) 💡 Key Learning: Higher Order Functions make code clean, readable, and scalable. Instead of writing long loops, we can write powerful one-line logic. 👉 Always remember: - "map()" → transforms data - "filter()" → selects data - "reduce()" → converts data into a single value Understanding these concepts is crucial for React, real-world projects, and technical interviews. 📌 Day 8 of consistent preparation — getting stronger with JavaScript fundamentals 🔥 #JavaScript #WebDevelopment #FullStackDeveloper #CodingJourney #MERNStack #InterviewPreparation #Frontend #Backend #LearnInPublic #Developers #Consistency #100DaysOfCode #LinkedIn #Connections