Most tutorials teach you what to build. Today I finally understood how things actually work under the hood. Day 4 of my React learning journey 🚀 Here’s what I worked on: • Built Create & Read functionality from scratch • Split logic into two separate components (cleaner + reusable) • Learned how to use React Hook Form • Understood how forms are managed efficiently using hooks Key insight: Handling forms in React doesn’t have to be messy. With the right approach (and tools like React Hook Form), you stop fighting state management… and start controlling it. Real moment: At first, managing inputs and state felt confusing — too many moving parts. But once I connected how hooks simplify the flow, everything started making sense. That shift from confusion → clarity was the real win today. Still early in the journey, but now I can see how real-world apps handle user data step by step. Building slowly. Understanding deeply. Devendra Dhote Sheryians Coding School #ReactJS #WebDevelopment #JavaScript #LearningInPublic #FrontendDev
React Forms Simplified with Hooks
More Relevant Posts
-
Day 10 of Learning React — Deep Dive into useEffect & useLayoutEffect Today was not about writing code… it was about understanding how React actually thinks 🧠 Here’s what I explored 👇 🔹 useEffect Basics Used for handling side effects (API calls, subscriptions, DOM updates) Runs after render 🔹 Dependency Array (Most Important Concept ⚠️) [] → Runs only once (Mount) [state] → Runs on state change (Update) No array → Runs on every render (⚠️ Dangerous if misused) 🔹 Component Lifecycle (Simplified React Way) Mount → Component created Update → State/props change Unmount → Cleanup (very important for memory leaks) 🔹 Cleanup Function Prevents memory leaks Example: removing event listeners, clearing intervals 🔹 useLayoutEffect vs useEffect useEffect → Runs after paint (async, non-blocking) useLayoutEffect → Runs before paint (sync, blocks UI) 👉 Use useLayoutEffect only when you need DOM measurements or avoid flickering 🔹 Practical Learning Fetched data using API (axios) Managed state updates Understood render cycles 💡 Key Realization: React is not about components… it’s about managing side effects correctly If you misuse useEffect, your app may: ❌ Re-render infinitely ❌ Cause performance issues ❌ Create memory leaks 🔥 Still learning, still building. Next goal: Mastering state management & optimization #React #WebDevelopment #MERN #FrontendDevelopment #LearningInPublic #JavaScript #Developers
To view or add a comment, sign in
-
-
🚀 Thrilled to announce the launch of LearnJS – A Modern Learning Platform for JavaScript! After investing significant time and effort, I'm excited to share a project that combines cutting-edge web technologies with a passion for education. LearnJS is a thoughtfully designed, fully interactive web application featuring curated lessons of JavaScript, built with React and powered by Vite for lightning-fast performance. 🎯 Project Overview LearnJS is more than just another coding tutorial site. It's a modern, interactive learning experience designed to break down complex JavaScript concepts into digestible, practical lessons. Built with React's component-driven architecture and Vite's blazing-fast development experience, this platform delivers both educational value and technical excellence. Whether you're a complete beginner taking your first steps into programming or an experienced developer looking to deepen your JavaScript knowledge, this platform has something for you. Live Platform: https://lnkd.in/gn4i4nJa GitHub Repository: https://lnkd.in/gUwnkBW9
To view or add a comment, sign in
-
-
🚀 Day 4 of Learning React — Understanding children Props Today I hit one of those small mistakes, big lesson moments while working with React. I was passing content inside a component like this: <Button>Next ➡</Button> But nothing showed up on the UI. 🤯 After debugging, I realized the issue wasn’t React… it was me. 👉 I had written childern instead of children. 💡 So what exactly is children in React? children is a special prop in React that allows you to pass content inside a component. function Button({ children }) { return <button>{children}</button>; } This makes your components: 🔁 Reusable 🎯 Flexible 🧩 Composable 🧠 Why it matters Instead of hardcoding content: ❌ Bad: <button>Click Me</button> ✅ Better: <Button>Click Me</Button> <Button>Submit</Button> <Button>Next ➡</Button> One component → multiple use cases. 🔥 My Key Takeaway Sometimes bugs are not about logic… they are about attention to detail. A single typo (childern) can break your UI silently. 🛠️ Debugging Habit I’m Building Whenever something doesn’t render: console.log(props); This simple step can save a lot of time. Day 4 done ✔️ Learning React is slowly shifting from confusion → clarity. #ReactJS #FrontendDevelopment #JavaScript #100DaysOfCode #LearningInPublic
To view or add a comment, sign in
-
🚀 I started learning React out of curiosity… but it completely changed how I think about building applications. At first, it felt overwhelming: – Components everywhere – Props vs State confusion – Hooks that made no sense But once things clicked, everything changed. 💡 React isn’t just a library for building UI — it’s a way of thinking. You stop writing messy, repetitive code and start building: ✔ Reusable components ✔ Clean and scalable structures ✔ Predictable UI logic And then you realize something powerful: 👉 Good React code is not about making things work 👉 It’s about making things maintainable But here’s the truth most people ignore: ⚠️ React is easy to start, but difficult to master. You’ll face: – Unnecessary re-renders – Complex state management – Confusing project structures And that’s where real growth begins. Right now, I’m focusing on: – Writing cleaner components – Improving performance – Understanding hooks deeply If you're learning React, don’t rush. Build. Break. Debug. Repeat. One day, it will all make sense. #ReactJS #FrontendDevelopment #JavaScript #WebDevelopment #CodingJourney #DeveloperGrowth #TechLearning
To view or add a comment, sign in
-
-
Day 46 – React Learning Journey Today’s focus was on understanding different ways to use functions in React event handling and how they impact code structure and flexibility. - Explored multiple approaches: Passing function references directly → onClick={handleClick} Using inline arrow functions → onDoubleClick={() => {...}} Handling mouse events → onMouseEnter, onMouseMove Working with input events and event objects → onChange={(e) => ...}- * Key Insight: Choosing the right way to use functions in events improves code readability, reusability, and performance. Understanding when to use direct references vs inline functions is essential for writing clean React code. - Every small concept like this builds a strong foundation for scalable frontend applications. github link : https://lnkd.in/gRbcs2Ue #Day46 #ReactJS #JavaScript #FrontendDevelopment #MERNStack #WebDevelopment #CleanCode #LearningInPublic
To view or add a comment, sign in
-
🚀 Day 8 of My React Learning Journey Today I faced a problem that every React developer eventually runs into… 👉 Props Drilling 💡 What I learned: Passing data from parent → child → child → child… just to reach one component 😵 At first, it seems fine. But as the app grows, it becomes: • Messy • Hard to manage • Difficult to scale 🧠 The Realization: Not every problem should be solved with props. Sometimes, the issue is not the code… It’s the approach. 🌐 Got introduced to: Context API Through my learning at Sheryians Coding School (Kodex Batch), I took a glimpse into how React solves this problem. 👉 Context API allows you to: • Share data globally • Avoid unnecessary prop passing • Keep components cleaner ⚙️ What changed in my thinking: Before: → “How do I pass data down?” Now: → “Do I even need to pass it through every component?” 🔥 Key Takeaways: • Props drilling is okay for small apps • But not scalable for larger systems • Context API helps manage shared state • Clean architecture > quick solutions 📈 What’s next: I’m going to: • Dive deeper into Context API • Build something using it • Understand when NOT to use it Every day I’m trying to move from: Writing React → Understanding React Architecture If you’re on the same journey or building something exciting, let’s connect 🤝 Devendra Dhote #React #JavaScript #FrontendDevelopment #WebDevelopment #LearningInPublic #100DaysOfCode
To view or add a comment, sign in
-
🚀 Day 16 of My JavaScript Journey Today was a powerful learning day 💻🔥 I explored some core JavaScript concepts that are extremely important for real-world applications. ✨ Topics I Covered: 🔹 Synchronous vs Asynchronous code 🔹 How the JavaScript Event Loop works 🔁 🔹 Why Callback Hell is a problem 😵 🔹 Creating Promises using "resolve" and "reject" 🤝 🔹 ".then()", ".catch()", ".finally()" methods 🔹 Sequential vs Parallel Promise execution ⚡ 🔹 Comparison of Promise utility methods 🔹 Real-world example: Food Delivery App (Zomato Clone 🍔) 🔹 API fetching using Promises 🌐 🔹 Error handling patterns 🚨 💡 Key Learning: Understanding asynchronous JavaScript is a game-changer 💯 Concepts like the Event Loop and Promises help write cleaner, more efficient, and scalable code. 🍽️ The food delivery app example helped me understand how multiple tasks like ordering, payment, and delivery can run efficiently using async concepts. 🔥 Growing step by step every day! Consistency is the key 🔑 #JavaScript #WebDevelopment #CodingJourney #DaysOfCode #AsyncJS #Promises #Learning #DeveloperLife
To view or add a comment, sign in
-
-
If you're learning React and still confused about hooks… You're not alone. 👉 A lot of people know how to use hooks, but not when to use them. And that’s where things start going wrong. Here are 5 React hooks that actually matter 👇 🔹 useState Manages component state and triggers re-render when data changes. Used in almost every app , but overusing it can make your logic messy. 🔹 useEffect Handles side effects like API calls and external updates. Most misused hook , bad dependencies = bugs + performance issues. 🔹 useRef Stores values without causing re-renders and accesses DOM directly. Super useful for focus control, timers, and tracking previous values. 🔹 useContext Removes prop drilling by sharing data across components. Great for global state , but don’t treat it like a full state manager. 🔹 useNavigate Controls navigation programmatically inside your app. Commonly used for redirects after login, logout, or form actions. --- Here’s the truth 👇 React isn’t hard. Bad understanding of hooks is. Stop memorizing. Start building. 💬 Which hook confused you the most when you started? #ReactJS #FrontendDeveloper #JavaScript #MERNStack #WebDevelopment #Coding #LearnInPublic
To view or add a comment, sign in
-
-
Building Confidence in React: Why Small Wins Matter Confidence in React didn’t come from watching more tutorials. It came from small, repeated wins. At first, everything felt confusing. Components, props, state, hooks… it was a lot. But instead of trying to master everything at once, I started focusing on small tasks: • Rendering a simple component • Passing data with props • Managing basic state • Fixing one bug at a time Each small win made the next step easier. What I’ve learned is this: confidence isn’t built in big moments. It’s built in quiet progress. Writing code that works. Fixing errors. Understanding one concept a little better than yesterday. Those small improvements compound. Now, when I approach a new feature or problem, I don’t feel overwhelmed. I break it down, just like I’ve been practicing. If you’re learning React (or any skill), don’t underestimate small wins. They’re doing more for your growth than you realize. #ReactJS #FrontendJourney #TechMindset #ProgrammingJourney #Developers
To view or add a comment, sign in
-
🚀 Day 9 of My React Learning Journey Today things got serious. I didn’t just learn Context API… I went deep into how it actually works. --- 💥 The moment it clicked: Props drilling is not just annoying… It’s a scaling problem. And today I finally understood: 👉 How React lets you share data without passing it everywhere --- 🧠 What I learned (real understanding): • How to create context • How to provide data globally • How components can consume data directly • Why this approach makes apps cleaner & scalable --- ⚙️ The shift in my thinking: Before: → “Pass data step by step” Now: → “Make data available where it’s needed” --- 🔥 But here’s the truth most tutorials won’t tell you: Context API is not just a feature… It’s the beginning of understanding state architecture. --- 📈 Why this matters: This is where you stop being a beginner and start thinking like someone who can build real applications --- 🚧 This is just the beginning… Next, I want to: • Build a project using Context API • Understand performance implications • Learn when NOT to use it --- 💡 Every day I’m moving from: Learning React → Thinking in systems If you’re also on this journey or building something meaningful, let’s connect 🤝 Devendra Dhote Sheryians Coding School #React #JavaScript #FrontendDevelopment #WebDevelopment #LearningInPublic #100DaysOfCode
To view or add a comment, sign in
Explore content categories
- Career
- Productivity
- Finance
- Soft Skills & Emotional Intelligence
- Project Management
- Education
- Technology
- Leadership
- Ecommerce
- User Experience
- Recruitment & HR
- Customer Experience
- Real Estate
- Marketing
- Sales
- Retail & Merchandising
- Science
- Supply Chain Management
- Future Of Work
- Consulting
- Writing
- Economics
- Artificial Intelligence
- Employee Experience
- Workplace Trends
- Fundraising
- Networking
- Corporate Social Responsibility
- Negotiation
- Communication
- Engineering
- Hospitality & Tourism
- Business Strategy
- Change Management
- Organizational Culture
- Design
- Innovation
- Event Planning
- Training & Development