International JavaScript Conference’s Post

Most “architecture debates” I’ve seen are really just naming debates. If the name is vague, people implement different things. If the name is too specific, you can’t evolve it. If the name is honest, the codebase gets calmer. Small trick: name things by the *decision they hide*, not by the *tech they use*. What’s the hardest thing you’ve had to name lately? #javascript #nodejs #reactjs #softwareengineering #cleancode

================================== enum and export type difference in TypeScript 😊 ================================== 🔹 enum - Creates a real JavaScript object after compilation. - Exists at runtime. - Generates additional JavaScript code. - The whole enum object is included in the bundle, even if you use only one value. - Can slightly increase bundle size. 🔹 export type - Used only for type checking. - Exists only during development (compile time). - Completely removed after compilation. - Generates no JavaScript output. - Helps reduce bundle size. simple way to say 💡 --------------------- enum → Runtime + JS Object export type → Compile-time only #TypeScript #Frontend #JavaScript #WebDevelopment #Learning #ReactJS #FrontendDevelopment #WebDevelopment #JavaScript #UILogic #FrontendEngineer #SoftwareDevelopment #TechLearning #CodingLife #100DaysOfCode #LinkedInTech 😊

𝐘𝐨𝐮 𝐂𝐚𝐧’𝐭 𝐒𝐤𝐢𝐩 𝐭𝐡𝐞 𝐏𝐨𝐰𝐞𝐫 𝐒𝐨𝐮𝐫𝐜𝐞 Early frontend me: “𝐈’𝐥𝐥 𝐬𝐤𝐢𝐩 𝐉𝐚𝐯𝐚𝐒𝐜𝐫𝐢𝐩𝐭 𝐚𝐧𝐝 𝐥𝐞𝐚𝐫𝐧 𝐑𝐞𝐚𝐜𝐭 𝐝𝐢𝐫𝐞𝐜𝐭𝐥𝐲.” Reality check: 𝐄𝐯𝐞𝐫𝐲 𝐟𝐫𝐚𝐦𝐞𝐰𝐨𝐫𝐤, 𝐥𝐢𝐛𝐫𝐚𝐫𝐲, 𝐚𝐧𝐝 𝐬𝐡𝐢𝐧𝐲 𝐭𝐨𝐨𝐥 𝐢𝐬 𝐬𝐭𝐢𝐥𝐥 𝐩𝐥𝐮𝐠𝐠𝐞𝐝 𝐢𝐧𝐭𝐨 𝐭𝐡𝐞 𝐬𝐚𝐦𝐞 𝐜𝐨𝐫𝐞. React, Next.js, Angular, Vue, TypeScript— they all draw power from JavaScript fundamentals. Lesson learned the traditional way: Strong basics make advanced tools easier, cleaner, and scalable. Shortcuts feel fast, but foundations compound. Build depth first. Frameworks can wait. #FrontendDevelopment #JavaScript #WebDevelopment #DeveloperJourney #ProgrammingBasics #LearnTheFundamentals #TechReality #CareerGrowth

👉 Event Loop in Node.js JavaScript is single threaded, but Node.js can handle many tasks at the same time. This is possible because of the Event Loop. 👉 What Event Loop does -Continuously checks if the call stack is empty -Picks the next task from queues -Executes it without blocking the main thread 👉 How it works -Synchronous code runs in the call stack -Async tasks like timers, file system, and APIs go to background Once the stack is empty, Event Loop pushes tasks back to execution 👉 Execution order -Microtask queue → Promises, process.nextTick -Timers queue → setTimeout, setInterval -I O queue → file system, network calls -Check queue → setImmediate 👉 Why it matters -Handles thousands of requests efficiently -Keeps the application fast and non blocking 👉 Key point Node.js is single threaded, but highly concurrent because of the Event Loop. #nodejs #javascript #eventloop #backenddevelopment #webDevelopment

Without strong basic of JavaScript you will get so lost into the complexity of frameworks that you might quit easily

You Can’t Skip the Power Source Early frontend me: “I’ll skip JavaScript and learn React directly.” Reality check: Every framework, library, and shiny tool is still plugged into the same core. React, Next.js, Angular, Vue, TypeScript— they all draw power from JavaScript fundamentals. Lesson learned the traditional way: Strong basics make advanced tools easier, cleaner, and scalable. Shortcuts feel fast, but foundations compound. Build depth first. Frameworks can wait. #FrontendDevelopment #JavaScript #WebDevelopment #DeveloperJourney #ProgrammingBasics #LearnTheFundamentals #TechReality #CareerGrowth

You Can’t Skip the Power Source Early frontend me: “I’ll skip JavaScript and learn React directly.” Reality check: Every framework, library, and shiny tool is still plugged into the same core. React, Next.js, Angular, Vue, TypeScript— they all draw power from JavaScript fundamentals. Lesson learned the traditional way: Strong basics make advanced tools easier, cleaner, and scalable. Shortcuts feel fast, but foundations compound. Build depth first. Frameworks can wait. #FrontendDevelopment #JavaScript #WebDevelopment #DeveloperJourney #ProgrammingBasics #LearnTheFundamentals #TechReality #CareerGrowth

Why I stopped using *ngIf and *ngFor in Angular 🧹 Angular has changed a lot recently, and one of my favorite updates is the new Built-in Control Flow. If you are still using the asterisk syntax (like *ngIf), here is why you should consider switching: Why the new syntax (@if, @for) is better: ✅ Easier to read: It looks like standard JavaScript/TypeScript code. ✅ Better Performance: It’s faster for the Angular compiler to process. ✅ No Imports: You don't need to import CommonModule anymore to use them! ✅ Built-in @empty: The @for loop now has a built-in way to show a message if a list is empty. No more extra *ngIf checks! A quick look at the difference: Old way: <div *ngIf="isLoggedIn">Welcome!</div> New way: @if (isLoggedIn) { <div>Welcome!</div> } It’s a small change that makes a huge difference in how clean our HTML templates look. Are you still using the traditional structural directives, or have you migrated to the new @ syntax? #Angular #WebDevelopment #Frontend #CleanCode #CodingTips #AngularDeveloper

Why I stopped using *ngIf and *ngFor in Angular 🧹 Angular has changed a lot recently, and one of my favorite updates is the new Built-in Control Flow. If you are still using the asterisk syntax (like *ngIf), here is why you should consider switching: Why the new syntax (@if, @for) is better: ✅ Easier to read: It looks like standard JavaScript/TypeScript code. ✅ Better Performance: It’s faster for the Angular compiler to process. ✅ No Imports: You don't need to import CommonModule anymore to use them! ✅ Built-in @empty: The @for loop now has a built-in way to show a message if a list is empty. No more extra *ngIf checks! A quick look at the difference: Old way: <div *ngIf="isLoggedIn">Welcome!</div> New way: @if (isLoggedIn) { <div>Welcome!</div> } It’s a small change that makes a huge difference in how clean our HTML templates look. Are you still using the traditional structural directives, or have you migrated to the new @ syntax? #Angular #WebDevelopment #Frontend #CleanCode #CodingTips #AngularDeveloper