Rithish Krishna’s Post

For a few days, I was working on building a sticky Notes App using Node.js and Express.js, and instead of using plain HTML, I experimented with EJS (Embedded JavaScript templates). While doing that, I noticed some interesting differences between using static HTML and server-side templating with EJS: • With HTML, everything is static and separate • With EJS, I can dynamically render data directly from the backend • Passing variables from Express to views makes the app feel more “real-time” and flexible • Folder structure becomes more organized when separating routes, views, and logic • It feels closer to how real-world backend-driven applications work This project enhanced my understanding of how frontend and backend integrate more seamlessly through the use of templating engines. I would love to hear how others approach structuring Node.js + Express projects with EJS, and if there are any improvements or best practices you would recommend to make this setup more efficient or scalable. #Nodejs #Expressjs #EJS #BackendDevelopment #WebDevelopment #LearningByDoing

The Core Difference React.js: A flexible JavaScript library for building modular user interfaces. Next.js: A powerful React framework engineered for production-scale applications. Key Differences: • Rendering → React: CSR | Next.js: SSR, SSG & ISR • Routing → React: Requires extra libraries | Next.js: File-based routing • SEO → React: Limited | Next.js: Excellent • Performance → React: Manual optimization | Next.js: Built-in optimization • Features → React: Basic setup | Next.js: API routes, Image optimization & more When to choose what? ✅ Choose React for maximum flexibility and custom setups 🚀 Choose Next.js for speed, SEO, and production-ready apps 💬 Most modern projects today are moving toward Next.js. Which one are you currently using React or Next.js? 👇 #ReactJS #NextJS #WebDevelopment #FrontendDeveloper #JavaScript #WebDev #Programming

Day 25 of my JavaScript journey 🚀 Built a Recipe Finder App using HTML, CSS, and JavaScript, powered by an external API. Features: 🍽️ Search recipes dynamically 🌐 Fetch data from TheMealDB API 📄 Display recipe details in real-time ✨ Interactive and user-friendly UI This project helped me understand how to work with APIs, handle asynchronous JavaScript, and build real-world applications. 🔗 Live Demo: https://lnkd.in/gSAAATzM 💻 GitHub Repo: https://lnkd.in/gBQmmBYJ Moving beyond basic projects and building applications that interact with real data. 💻 #JavaScript #WebDevelopment #FrontendDeveloper #100DaysOfCode #CodingJourney #API

🚀 Understanding useEffect in React — Simplified! If you're working with React, mastering useEffect is not optional— 👉 It controls how your app interacts with the outside world. 💡 What is useEffect? useEffect is a hook that lets you perform side effects in components. 👉 Side effects include: API calls Event listeners Timers DOM updates ⚙️ Basic Syntax useEffect(() => { // side effect logic }, [dependencies]); 🧠 How it works 1️⃣ Runs after component renders 2️⃣ Re-runs when dependencies change 3️⃣ Cleanup runs before next effect or unmount 🔹 Example useEffect(() => { console.log("Component mounted or updated"); }, []); 👉 Runs only once (on mount) 🔹 With Dependency useEffect(() => { console.log("Count changed"); }, [count]); 👉 Runs when count changes 🔹 Cleanup Function useEffect(() => { const timer = setInterval(() => { console.log("Running..."); }, 1000); return () => clearInterval(timer); }, []); 👉 Prevents memory leaks 🧩 Real-world use cases ✔ Fetching API data ✔ Subscribing to events ✔ Setting intervals / timeouts ✔ Syncing with external systems 🔥 Best Practices (Most developers miss this!) ✅ Always use dependency array correctly ✅ Cleanup side effects properly ✅ Split multiple effects into separate useEffects ❌ Don’t ignore dependencies (can cause bugs) ❌ Don’t overuse useEffect unnecessarily ⚠️ Common Mistake useEffect(() => { fetchData(); }, []); 👉 If fetchData depends on props/state → can cause bugs 💬 Pro Insight useEffect is not just about running code— 👉 It’s about syncing your component with external systems 📌 Save this post & follow for more deep frontend insights! 📅 Day 13/100 #ReactJS #FrontendDevelopment #JavaScript #ReactHooks #useEffect #WebDevelopment #SoftwareEngineering #100DaysOfCode 🚀

Stop watching tutorials — start building real full-stack projects. These projects with source code will help you practice, learn faster, and build a strong portfolio 🚀 👉 Comment “PROJECT” and I’ll send you the source code. full stack projects with source code, web development projects, mern stack projects, full stack developer portfolio, coding projects for beginners, real world web projects, frontend backend projects #FullStackDeveloper #WebDevelopment #CodingProjects #JavaScript #DeveloperLife

⚛️ How React Re-Renders Components (Simple Explanation) While working with React, one thing I was always curious about was: 👉 What actually happens when a component re-renders? Here’s a simple way I understand it 👇 🔹 What triggers a re-render? A component re-renders when: • state changes • props change • parent component re-renders 🔹 What happens during a re-render? React doesn’t directly update the DOM. Instead: 1️⃣ It creates a new Virtual DOM 2️⃣ Compares it with the previous version (diffing) 3️⃣ Updates only the changed parts in the real DOM This process is called Reconciliation 🔹 Why this matters Understanding this helps you: ✅ avoid unnecessary re-renders ✅ optimize performance ✅ write more efficient components 🔹 Common mistake A parent re-render can cause all child components to re-render — even if their data hasn’t changed. That’s where optimizations like: • React.memo • useMemo • useCallback become useful. 💡 One thing I’ve learned: React is fast — but understanding how it works internally helps you make it even better. Curious to hear from other developers 👇 What strategy do you use to prevent unnecessary re-renders? #reactjs #frontenddevelopment #javascript #webdevelopment #softwareengineering #developers

🚀 React Re-rendering — Key Concepts Re-rendering is the core of how React keeps UI in sync with data. Without it, there would be no interactivity in our applications. Here are some important insights I've learned: 🔹 State updates are the primary trigger for re-renders 🔹 When a component re-renders, all its child components re-render by default 🔹 Even without props, components still re-render during the normal render cycle (without use of memoization). 🔹 Updating state in a hook triggers a re-render, even if that state isn’t directly used 🔹 In chained hooks, any state update will re-render the component using the top-level hook 🔹 “Moving state down” is a powerful pattern to reduce unnecessary re-renders in large applications #ReactJS #FrontendDevelopment #WebDevelopment #JavaScript #SoftwareEngineering #LearningInPublic

🚀 Controlled vs Uncontrolled Components in React — Real-World Perspective Most developers learn: 👉 Controlled = React state 👉 Uncontrolled = DOM refs But in real applications… 👉 The choice impacts performance, scalability, and maintainability. 💡 Quick Recap 🔹 Controlled Components: Managed by React state Re-render on every input change 🔹 Uncontrolled Components: Managed by the DOM Accessed via refs ⚙️ The Real Problem In large forms: ❌ Controlled inputs → Too many re-renders ❌ Uncontrolled inputs → Hard to validate & manage 👉 So which one should you use? 🧠 Real-world Decision Rule 👉 Use Controlled when: ✔ You need validation ✔ UI depends on input ✔ Dynamic form logic exists 👉 Use Uncontrolled when: ✔ Performance is critical ✔ Minimal validation needed ✔ Simple forms 🔥 Performance Insight Controlled input: <input value={name} onChange={(e) => setName(e.target.value)} /> 👉 Re-renders on every keystroke Uncontrolled input: <input ref={inputRef} /> 👉 No re-render → better performance ⚠️ Advanced Problem (Most devs miss this) 👉 Large forms with 20+ fields Controlled approach: ❌ Can slow down typing 👉 Solution: ✔ Hybrid approach ✔ Use libraries (React Hook Form) 🧩 Industry Pattern Modern apps often use: 👉 Controlled logic + Uncontrolled inputs internally Example: ✔ React Hook Form ✔ Formik (optimized patterns) 🔥 Best Practices ✅ Use controlled for logic-heavy forms ✅ Use uncontrolled for performance-critical inputs ✅ Consider form libraries for scalability ❌ Don’t blindly use controlled everywhere 💬 Pro Insight (Senior Thinking) 👉 This is not about “which is better” 👉 It’s about choosing the right tool for the problem 📌 Save this post & follow for more deep frontend insights! 📅 Day 17/100 #ReactJS #FrontendDevelopment #JavaScript #ReactHooks #PerformanceOptimization #SoftwareEngineering #100DaysOfCode 🚀

I Just built and deployed a Weather App 🌤️ This project helped me understand how to work with APIs and handle real-time data using JavaScript… Features include: • Search weather by city • Real-time temperature and conditions • Weather icons • Clean and responsive UI (though basic) Try it here: 👉 https://lnkd.in/ea_SveTQ View code: 👉 https://lnkd.in/ervqjNiN More projects coming — currently building and improving daily 🚀 #FrontendDeveloper #JavaScript #WebDevelopment #BuildInPublic

𝐈𝐬 𝐑𝐞𝐚𝐜𝐭 𝐚 𝐟𝐫𝐚𝐦𝐞𝐰𝐨𝐫𝐤 𝐨𝐫 𝐚 𝐥𝐢𝐛𝐫𝐚𝐫𝐲? I used to genuinely not know the answer to this. I kept hearing both and just... went along with it. Until I actually looked it up. First stop - the official React docs at https://react.dev. Right there on the homepage it calls itself "the library for web and native user interfaces." Then I checked MDN https://lnkd.in/gTP_zAW4, which is basically the bible for web developers. Same answer - React is a library, not a framework. They even say it outright: "React is not a framework." So what's the actual difference? React only handles the UI layer. That's it. No routing built in, no state management system, nothing like that. You pull in other tools for those things yourself. A framework would give you all of that out of the box - think structure vs. flexibility. That's why React feels like a framework when you're using it in a big project. But technically, it's not. Honestly, once that clicked, the way I think about frontend tools completely changed. I stopped treating React like it was supposed to do everything and started understanding why we add libraries like React Router or Zustand alongside it. Sometimes the confusion isn't about how hard something is - it's just that nobody explained the basics clearly enough from the start. #React #FrontendDevelopment #JavaScript #WebDevelopment #LearningInPublic