Day 67: Async/Await in JavaScript Mastery

🚀 Day 2/100 JavaScript #100daysofcodechallenge 🚀 📌 Today’s Progress: Today I built two small JavaScript programs. The first program is a Trivia Bot. The bot introduces itself, shares some coding fun facts, and prints messages to the console using variables and string concatenation. The second program is a Sentence Maker. It creates short stories by combining words stored in variables like adjectives, nouns, verbs, and places. I also created a third sentence that introduces me, my age, what I study, and my life goal. This project helped me practice variables, string concatenation, and how programs generate dynamic sentences. Small projects like this train my thinking as a developer. I am learning how code can turn simple data into meaningful output. I added something new. I learnt sometimes GitHub repositories without READMEs is a bad practice so this time I added a README to my repository. Day 2. Still learning. Still building. Check it out on my GitHub: https://lnkd.in/d-jdmyVy Screenshots of codes are below. #100DaysOfCode #CodetrainAfrica #codetrainafrica #Gen31 #JavaScript #WebDevelopment #CodingJourney #LearnToCode #SoftwareEngineering #FrontendDevelopment #FullStackDevelopment #CodingLife #DevCommunity #BuildInPublic #TechLearning #Programming #Developers #CareerInTech #Everydaycoding #Technology #JavaScriptForBeginners Richard Brandt Sam Generals William Brandt Boateng Harrison Joshua Doe Foster Frimpong Flora Dadie

I started solving the GitHub Classroom assignments for Async JavaScript. And something surprising happened… Each question felt like solving a real-world problem, not just writing code. While working on the assignment, I realized something important. Good programming problems don't just test syntax. They simulate real scenarios developers face in production. For example: • Handling async operations • Managing data like real sales records • Understanding this context issues • Writing logic that actually solves a business problem Instead of memorizing JavaScript concepts, I felt like I was building solutions. That’s when learning becomes powerful. Huge thanks to Hitesh Choudhary sir and the #ChaiCode community for creating assignments that feel like real developer work, not textbook exercises. Learning this way makes coding far more enjoyable. If you're learning JavaScript, try this approach: • Solve real-world style problems • Write tests for your code • Focus on problem solving, not just syntax Piyush Garg | Akash Kadlag | Suraj Kumar Jha | Shubham Waje

🚀 Day 2 of My Coding Journey Today I practiced an important concept: Reversing a String and a Number using Functions in JavaScript 🔹 What I learned: How to reverse a string using a loop How to reverse a number using mathematical logic Also explored shortcut methods using built-in functions 💻 Example: Reversing a String function reverseString(str) { let reversed = ""; for (let i = str.length - 1; i >= 0; i--) { reversed += str[i]; } return reversed; } Reversing a Number function reverseNumber(num) { let reversed = 0; while (num > 0) { let digit = num % 10; reversed = reversed * 10 + digit; num = Math.floor(num / 10); } return reversed; } 📌 Key Takeaway: Understanding logic is more important than just using built-in methods. I’m improving step by step every day 💪 #Day2 #JavaScript #CodingJourney #WebDevelopment #90DaysOfCode #Learning #FrontendDeveloper

Completing my JavaScript roadmap wasted my time I thought I had escaped tutorial hell when I was learning JavaScript last year because I was learning through a structured roadmap with documentation. And still couldn't build anything on my own. My coding mentality has now shifted from “complete the roadmap” to “have the ability to build anything you think of” and this is the mindset I currently use to learn TypeScript. Here is everything I am doing to measure my progress and hit my goal: => I always plan and understand what I want to build before I write a single line of code (bye bye spaghetti code!) => I start with small projects especially ones I am familiar with, this helps me understand the language’s patterns quicker => I gradually increase project difficulty to challenge my growth => I time myself every time to track my progress speed-wise => I always build what I love, any idea that comes to mind => I take building in public seriously => Document every new thing I learn, not the syntax but approach and logic Now I can easily track my progress and know what gaps need filling. Making progress in learning a programming language is no different from learning any human language, it simply means getting stuff done with it. It’s more about how you can think in that language, not how much syntax you’ve covered. What made you know you had a strong grasp of a programming language you were learning? 

I used to start coding without thinking… And got stuck every single time. 😅 Then I discovered something simple: "Pseudocode". 👉 It’s just writing your logic in plain English before coding. This small habit changed everything for me: ✔ Clear thinking ✔ Fewer errors ✔ Faster coding If you're a beginner, try this once before coding 👇 You’ll see the difference. #coding #webdevelopment #beginners #javascript #learninginpublic #dataStructure

🚀 Day 35 — A Question That Led Me to TypeScript Today, I didn’t just code… 👉 I learned how to think. While working with JavaScript, a simple question came to my mind: “JavaScript is so powerful… then why does it still cause so many bugs?” To find the answer, I explored this topic using Sheryians Coding School (Cohort 2.0) as my reference. 📌 What I Observed Today: JavaScript performs type coercion (automatic type conversion), which sometimes leads to unexpected results 👇 "string" + number → string "string" - number → number "string" * number → number boolean + number → number [] + 1 → "1" [1,2] + 1 → "1,21" [] == false → true 👉 These behaviors are valid in JavaScript… but in real-world applications, they can become hidden bugs. ⚠️ Problem I Understood: JavaScript is dynamically typed, which means: Type errors are not caught early Debugging becomes difficult Code becomes unpredictable 💡 Why I Started TypeScript Today: I thought… 👉 “If the problem is this clear, there must be a solution.” And that curiosity pushed me to start learning TypeScript. 🚀 What TypeScript Solves: Provides static typing Detects errors at compile time Makes code more predictable Helps manage large-scale applications 🙏 Special Thanks to My Mentors: • Ankur Prajapati bhaiya • Harsh Vandana Sharma bhaiya • Sarthak Sharma bhaiya • Dhanesh Parwati Malviya bhaiya • Satwik Raj bhaiya • Sheryians Coding School Community 🔥 Key Takeaway: “JavaScript gives freedom, TypeScript gives control.” #Day35 #TypeScript #JavaScript #LearnInPublic #CodingJourney #Developers #WebDevelopment

🔥 Day 13/100 — Mastering JavaScript Essentials 🚀 Today I revisited 3 absolute game-changers in JavaScript: map, filter, and reduce — the holy trinity of clean, functional code 💡 Here’s a quick breakdown 👇 ✨ map() — Transform Data Used when you want to modify every element in an array. 👉 Example: const nums = [1, 2, 3]; const squared = nums.map(n => n * n); // [1, 4, 9] 🧹 filter() — Select Data Used to keep only elements that match a condition. 👉 Example: const nums = [1, 2, 3, 4]; const evens = nums.filter(n => n % 2 === 0); // [2, 4] 🧠 reduce() — Aggregate Data Used to boil down an array into a single value. 👉 Example: const nums = [1, 2, 3, 4]; const sum = nums.reduce((acc, n) => acc + n, 0); // 10 💥 The real power? Combining them: const result = [1,2,3,4,5] .filter(n => n % 2 !== 0) .map(n => n * 2) .reduce((acc, n) => acc + n, 0); // Output: 18 ⚡ Cleaner code ⚡ Less loops ⚡ More readability It’s crazy how mastering these small concepts can level up your coding style BIG TIME 🚀 #100DaysOfCode #JavaScript #WebDevelopment #CodingJourney #Developers #LearnInPublic #Tech #Programming #LearningInPublic Sheryians Coding School Sheryians Coding School Community

🚀 Diving into JavaScript Functions! 🚀 Functions are like recipes in programming 🍳 They are blocks of code that perform a specific task when called. Developers use functions to organize code, make it reusable, and improve readability. Understanding functions is essential for every developer to write efficient and maintainable code. Let's break it down: 1️⃣ Declare a function using the keyword "function" followed by a name and parameters. 2️⃣ Write the code block inside curly braces to define what the function does. 3️⃣ Call the function by using its name and passing any required arguments. Check out this example: ```javascript function greet(name) { return `Hello, ${name}!`; } console.log(greet("Alice")); ``` Pro Tip: Don't forget to use meaningful function names and keep them concise for better code organization. 🌟 Common Mistake Alert: Forgetting to return a value from the function can lead to unexpected behavior. Always ensure your functions explicitly return a value when needed. 🤔 What's your favorite function to write and why? Share in the comments below! 🤓 🌐 View my full portfolio and more dev resources at tharindunipun.lk #JavaScriptFunctions #CodeOrganization #ReusableCode #WebDevelopment #LearnToCode #ProgrammingTips #FunctionBestPractices #TechTutorials #DeveloperCommunity

🚀 Day 36 — Turning TypeScript Concepts into Practical Understanding Yesterday, I understood the problems in JavaScript… 👉 Today, I focused on how TypeScript actually solves them through real code. Instead of just reading theory, I practiced multiple examples from my learning resource — Sheryians Coding School (Cohort 2.0) 📌 What I Explored Today: Today’s focus was on applying TypeScript in real scenarios: 🔹 Typed Variables Defining clear types like string, number, boolean → So the system knows exactly what kind of data it is handling 🔹 Functions with Types Adding types to parameters Defining return types 👉 This ensures functions behave exactly as expected 🔹 Type Safety in Operations TypeScript prevents mixing incompatible types → No more unexpected outputs like in JavaScript 🔹 Error Detection Before Execution JavaScript → Errors at runtime TypeScript → Errors at compile time 👉 This alone makes development more reliable. 💻 What I Noticed Practically: While working on different code snippets today: TypeScript was constantly guiding me It highlighted mistakes instantly It forced me to write cleaner and more structured code 👉 It felt like having a real-time assistant while coding ⚠️ Big Difference I Realized: JavaScript: Flexible but risky Easy to write, hard to maintain TypeScript: Slightly strict but safer Better for scaling applications 💡 My Understanding Now: TypeScript is not about restricting developers… 👉 It’s about helping developers avoid mistakes before they happen. 🙏 Special Thanks to My Mentors: • Ankur Prajapati bhaiya • Harsh Vandana Sharma bhaiya • Sarthak Sharma bhaiya • Dhanesh Parwati Malviya bhaiya • Satwik Raj bhaiya • Sheryians Coding School Community 🔥 Key Takeaway: “Good code is not just about working code, it’s about predictable and safe code.” #Day36 #TypeScript #JavaScript #LearnInPublic #CodingJourney #Developers #WebDevelopment

Day 16 of my 21 Days Learning Challenge Today I revisited a core JavaScript concept — Execution Context and Call Stack. While writing JavaScript code, it may look like everything runs line by line, but behind the scenes, JavaScript follows a structured process to execute code. 1️⃣ Execution Context An Execution Context is the environment where JavaScript code is executed. There are mainly two types: • Global Execution Context (GEC) → created when the program starts • Function Execution Context (FEC) → created whenever a function is called Each execution context goes through two phases: 1. Memory Creation Phase 2. Execution Phase 2️⃣ Memory Creation Phase In this phase: • variables are allocated memory (undefined) • functions are stored in memory Example: console.log(a); var a = 10; Here, a is initialized as undefined during the memory phase. 3️⃣ Execution Phase In this phase: • code runs line by line • values are assigned • functions are executed 4️⃣ Call Stack The Call Stack keeps track of function execution. It follows LIFO (Last In, First Out). Example: function one() { two(); } function two() { console.log("Hello"); } one(); Execution order: one() → two() → console.log() Functions are added to the stack when called and removed when execution is complete. 🔹 Why this matters Understanding execution context and call stack helps in: • debugging code • understanding hoisting • mastering async JavaScript Revisiting this concept helped me better understand how JavaScript executes code behind the scenes, not just how we write it. #21DaysChallenge #JavaScript #LearningInPublic #FrontendDevelopment #WebDevelopment #SheryiansCodingSchool Sheryians Coding School