Built a simple CRUD app using React Worked on a project where users can: Create posts (with image, title, description) View all posts in card format Edit posts without creating duplicates Delete posts instantly Learned: 1.State management with useState 2.Handling forms & file inputs 3.Conditional rendering 4.Updating vs creating data (real CRUD logic) 5.Simple project, but helped me understand React much better. #React #JavaScript #WebDevelopment #CRUD #LearningInPublic
More Relevant Posts
-
I kept wondering why my React app was calling the same API multiple times… 🤯 At first, I thought it was a small issue. But as the project grew, it became a real problem: * Repeated API calls * Too much state handling (loading, error, data) * Debugging became painful All because I was using `useEffect` for API calls. Then I tried something different — **React Query**. And honestly, it changed the way I handle server data: ✅ Automatic caching ✅ Built-in loading & error handling ✅ Cleaner, more maintainable code The biggest realization for me: 👉 *useEffect is not meant for managing server state.* I wrote a short article sharing what I learned and how I fixed these issues in a real project 👇 🔗 https://lnkd.in/gPMTcQBw If you're working with React, this might save you some debugging time. Would love to hear how you're handling API calls in your apps 👇 #React #JavaScript #PerformanceOptimization #WebDevelopment #ReactQuery
To view or add a comment, sign in
-
Behind the Screen – #34 Do you know? The #node_modules folder is often larger than your entire project. Why is it so big? 👉 Your project depends on many #packages 👉 Each package has its own #dependencies 👉 Those dependencies have their own dependencies This creates a dependency tree. So when you #install one library, you might actually be installing hundreds of smaller packages. Also: 👉 Packages include multiple files (code, configs, docs) 👉 Different versions may coexist 👉 Everything is stored #locally for faster usage That’s why node_modules grows so quickly. It may look heavy, but it helps your app run without fetching things again and again. 🔥 One install command can bring an entire ecosystem into your project. #javascript #reactjs #webdevelopment #techfacts #developer
To view or add a comment, sign in
-
🚀 Day 948 of #1000DaysOfCode ✨ Setting Up Redux in Next.js (The Right Way) State management in modern apps can get messy — especially when you’re working with frameworks like Next.js. In today’s post, I’ve shared a clean and practical setup of Redux in a Next.js application, so you can manage global state without confusion. From configuring the store to integrating it properly with your app structure, this setup ensures everything works smoothly with both client and server rendering. I’ve also focused on keeping the setup scalable, so you’re not just making it work — you’re building it the right way from the start. If you’re building real-world React or Next.js applications, understanding this setup will save you a lot of time and headaches later. 👇 What’s the most confusing part for you when setting up Redux in Next.js? #Day948 #learningoftheday #1000daysofcodingchallenge #FrontendDevelopment #WebDevelopment #JavaScript #React #Next #CodingCommunity #Redux #CodingCommunity
To view or add a comment, sign in
-
I’ve used both Redux and Context API in my React projects… and honestly, each has its place. ⚛️ In smaller apps, Context API feels simple and quick. But as things grow, I often switch to Redux for better structure and scalability. That’s something I’ve learned over time: The right choice depends on the project, not the trend. So I’m curious. What’s your go-to for state management? Redux or Context API? #ReactJS #Redux #ContextAPI #FrontendDevelopment #JavaScript
To view or add a comment, sign in
-
-
🚀 New Project: Interactive Joke Generator in Next.js! I just built a dynamic random joke app exploring the power of Next.js Client Components and State Management. Technical Highlights: 🏗️ Architecture: Organised with Route Groups (projects) for a clean, scalable folder structure. ⚡ Data Fetching: Leveraged async/await and useEffect to pull live data from the Official Jokes API. 🧠 State Control: Implemented useState for a smooth Reveal/Hide punchline toggle and "Next Joke" functionality. 🎨 Styling: Fully responsive UI built with Tailwind CSS integrated via globals.css. Understanding the "use client" boundary and preventing unnecessary re-renders was a great deep dive into React performance! #NextJS #ReactJS #WebDev #TailwindCSS #Coding #Javascript
To view or add a comment, sign in
-
I removed useEffect from my code… and my app got faster ⚡ Yes, seriously. For a long time, I was doing this in React: useEffect(() => { fetchUsers(); }, []); Seemed correct… right? ❌ But in real projects, this caused: • Multiple unnecessary API calls • Data mismatch bugs • Hard-to-control logic 💡 Then I changed my approach: Instead of auto-calling APIs inside useEffect, 👉 I started triggering APIs based on user actions Example: • Search → onChange • Button → onClick ✅ Result: • Better control over API calls • Cleaner component logic • Improved performance (~30% fewer calls) 🔥 What I learned: useEffect is powerful… but overusing it makes your code messy. 💬 Curious: Do you still rely on useEffect for API calls? #ReactJS #FrontendDeveloper #JavaScript #CodingTips #WebDevelopment
To view or add a comment, sign in
-
I removed useEffect from my code… and my app got faster ⚡ Yes, seriously. For a long time, I was doing this in React: useEffect(() => { fetchUsers(); }, []); Seemed correct… right? ❌ But in real projects, this caused: • Multiple unnecessary API calls • Data mismatch bugs • Hard-to-control logic 💡 Then I changed my approach: Instead of auto-calling APIs inside useEffect, 👉 I started triggering APIs based on user actions Example: • Search → onChange • Button → onClick ✅ Result: • Better control over API calls • Cleaner component logic • Improved performance (~30% fewer calls) 🔥 What I learned: useEffect is powerful… but overusing it makes your code messy. 💬 Curious: Do you still rely on useEffect for API calls? #ReactJS #FrontendDeveloper #JavaScript #CodingTips #WebDevelopment
To view or add a comment, sign in
-
🚀 Excited to share my latest project! I built a Notes App using JavaScript & LocalStorage that allows users to create, save, and delete notes efficiently. ✨ Key Features: • Add & delete notes • Data stored using LocalStorage • Simple and clean UI 🔗 Live Demo: https://lnkd.in/d_zt2ems This project helped me strengthen my understanding of DOM manipulation and browser storage. 💡 Next, I plan to add features like Edit, Search, and Dark Mode. #JavaScript #WebDevelopment #FrontendDeveloper #Projects #Learning
To view or add a comment, sign in
-
Most developers try to optimize React apps… without knowing what’s actually slow. That’s the problem. Before you optimize… You need to measure. That’s where the React Profiler comes in 🔍 ⚡ What is React Profiler? A tool (inside React DevTools) that shows: • Which components are re-rendering • How long each render takes • Why a component re-rendered 🧠 What it helps you discover • Unnecessary re-renders • Slow components • Expensive computations • Props/state changes causing re-renders 🔍 Real example You click a button and suddenly the whole page re-renders. Profiler shows: 👉 A parent component updated 👉 All child components re-rendered 👉 Even the ones that didn’t need to 🚀 How to fix (after profiling) • Wrap components with React.memo • Use useMemo for heavy calculations • Use useCallback for stable functions • Avoid passing new object/array references 💡 Biggest mistake Optimizing blindly. Adding memoization everywhere… without knowing if it even helps. Measure → Identify → Optimize That’s the correct flow. 💡 React performance is not about writing more code. It’s about writing smarter code based on data. Have you ever used React Profiler to fix a real issue? 👇 #React #Frontend #WebPerformance #JavaScript #SoftwareEngineering #WebDevelopment
To view or add a comment, sign in
-
𝗪𝗵𝘆 𝗬𝗼𝘂𝗿 𝗝𝗮𝘃𝗮𝘀𝗰𝗿𝗶𝗽𝘁 𝗙𝗲𝗲𝗹𝘀 𝗦𝗹𝗼𝘄 𝗔𝗻𝗱 𝗛𝗼𝘄 𝗠𝗮𝘀𝘁𝗲𝗿𝗶𝗻𝗴 𝗔𝘀𝘆𝗻𝗰 𝗪𝗶𝗹𝗹 𝗙𝗶𝘅 𝗜𝘁 Is your app freezing? The real reason is async JavaScript handled poorly. JavaScript runs on one thread. It does one task at a time. Async tasks let it handle many things without stopping. Here are the async tools you must know: - Promises: Manage tasks that finish later. - async/await: Write async code that reads step by step. - try...catch: Always catch errors. - Promise.all(): Run independent tasks at the same time. - Avoid long tasks on the main thread. My friend had a slow app. He fixed the async code. Load times dropped. The app stayed the same. The async handling improved. Use async/await for clearer code today. Your app does not need less work. It needs to work smarter. What part of async is hardest for you? Promises? async/await? Multiple tasks? Source: https://lnkd.in/gghEGCR8
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
Keep it up ! 👍