Learning React.js with Props and State

While learning React, I made a mistake that slowed me down… I used useEffect for everything. Fetching data Updating state Even simple calculations At first, it felt powerful. But soon my code became: Confusing Hard to debug Full of unnecessary logic Then I realized something important: 👉 Not everything belongs in useEffect Now I: • Keep logic simple • Avoid unnecessary state • Use hooks only when needed The biggest lesson: Clean code > clever code Curious to know: What confused you most while learning React? #ReactJS #FrontendDeveloper #WebDevelopment #JavaScript

Day 12–13 of my 30 Days Job-Ready Challenge Built a Todo App in React. It looks simple, but learned a lot while building it: Why we should not mutate state directly Difference between map() and filter() and where to use them Event bubbling (delete click was marking task complete 😅) Using localStorage to persist data The main learning was not coding. It was thinking before writing code. What state is needed? What should be its type? What happens on different user actions? Clear logic >>> writing code fast. Discipline builds consistency. #100DaysOfCode #ReactJS #Frontend #WebDevelopment #JavaScript #LearningInPublic

Yesterday I shared React tips for beginners. Today, here are 5 mistakes almost every React beginner makes 👇 1. Using array index as key Bad: `key={index}` Better: Use a unique id. 2. Changing state directly Wrong: `user.name = "John"` Always use: `setUser({...user, name: "John"})` 3. Forgetting dependency array in useEffect Without it, your effect may run again and again unexpectedly. 4. Creating one huge component Break your UI into smaller reusable components. 5. Passing too many props everywhere If data is shared across many components, use Context API or state management. I made all of these mistakes while learning React 😅 But once I fixed them, React became much easier. Which mistake have you made the most? #reactjs #javascript #frontend #webdevelopment #coding

Day 5 of Learning React JS 🚀 Today was all about going deeper into how React actually works behind the scenes. I focused on understanding state and props more clearly—and things are finally starting to click! Here’s what I explored today: 🔹 How state controls dynamic data inside components 🔹 Passing data using props and making components reusable 🔹 The importance of keeping components clean and modular 🔹 Practiced building a small interactive UI (and fixed a lot of bugs 😅) One key realization: React is less about memorizing syntax and more about thinking in components. It’s challenging at times, but also super rewarding when things start working the way you expect. Slowly building confidence step by step Looking forward to diving into hooks next! #ReactJS #WebDevelopment #LearningJourney #JavaScript #FrontendDevelopment #100DaysOfCode

🔹 React Basics: Props vs State (Explained Simply) When starting with React, one of the most important concepts to understand is the difference between Props and State. Here’s a simple breakdown 👇 👉 Props (Properties) • Passed from parent to child components • Read-only (cannot be modified) • Used to make components reusable 👉 State • Managed within the component • Can be updated using hooks like `useState` • Controls dynamic data and UI behavior 💡 In short: Props help you pass data, while State helps you manage data. Understanding this difference is key to building scalable and maintainable React applications. If you're learning React, mastering these fundamentals will make your journey much smoother 🚀 💬 What topic should I cover next in React? #ReactJS #FrontendDevelopment #JavaScript #WebDevelopment #LearningInPublic #SoftwareDevelopment #CodingJourney #Developers

📘 Mastering React JS Fundamentals & Core Concepts Continuously strengthening my front-end development skills, I’ve been diving deep into React JS fundamentals and organizing key concepts in a structured way. This learning covers: 🔹 React basics and component-based architecture 🔹 Understanding JSX and how it works behind the scenes 🔹 Difference between State vs Props and their roles in data handling 🔹 Hands-on practice with Hooks like `useState` and `useEffect` 🔹 React lifecycle and how components update efficiently using the Virtual DOM Building a strong foundation in these core concepts is essential for developing scalable and high-performance web applications. 🚀 Always learning, always improving. #ReactJS #WebDevelopment #FrontendDevelopment #JavaScript #CodingJourney #SoftwareDevelopment

React Learning Moment !! Today, while revising some React concepts I've studied before, I suddenly found myself stuck at the props.children concept. I spent a few minutes really focusing on it, and now I finally understand why it's so powerful and useful! In React, props.children allows a parent component to pass any nested content to a child component. This makes components flexible and reusable, letting you separate layout/styling from content. For example, in my practice project: The Parent component passes content. The Son and Daughter components render this content using {props.children}. Check out this simple diagram I made to visualize the flow 👇 . . . 📖: For more detail https://lnkd.in/d2ewC35h #ReactJS #WebDevelopment #LearningInPublic #JavaScript #FrontendDevelopment #CodingJourney

I went quiet for a bit… but not because I stopped learning. I’ve been spending the past couple of weeks getting deeper into Next.js and trying to understand things beyond just “making it work.” At this stage, I’m realizing something: The more you learn, the more you see what you don’t know. Moving from React into Next.js has pushed me to think differently about structure, performance, and how applications actually run, not just how they look. I’m no longer just focused on building features. I’m trying to understand why things work the way they do. Still learning. Still building. Just at a different level now. For developers here: what concept in Next.js took you the longest to understand? #NextJS #WebDevelopment #FrontendDeveloper #BuildInPublic #JavaScript

At one point, I thought I was ready. I knew the skills. JavaScript, React, APIs… I had learned a lot. But when it came to actually applying, there was still uncertainty. That’s when I realized: Knowing skills ≠ being ready I didn’t know where I stood. I didn’t know what I was missing. That gap matters more than people think. That’s something I’ve been exploring while building RoleReady. If you’re in a similar phase, you can check it here: https://roleready.org Also sharing more here: https://lnkd.in/dWw4eyWh

🚀 Learning Update | JavaScript, React & Consistency Here’s what I worked on recently: 🔹 JavaScript Fundamentals Implemented 5 practical examples to strengthen understanding of closures. 🔹 OOP in JavaScript Created a class with constructor and methods, and extended it into a subclass to understand inheritance. 🔹 DSA Practice Solved 4 LeetCode problems to improve problem-solving skills 💪 🔹 React Development Built a React-based form page and understood the advantages of using type="submit" for better form handling. 🔹 Node.js Practice Completed 5 Node.js challenges on HackerRank, improving backend fundamentals. 🔹 Communication Improvement Continued reading The Power of Subconscious Mind to enhance communication 🧠 Small, consistent efforts are building strong foundations. #JavaScript #ReactJS #NodeJS #DSA #LearningInPublic #GrowthMindset