CodingNovas’ Post

Learning coding is not the hard part Most people are just learning it the wrong way And that’s why it feels frustrating We’ve seen beginners spend months jumping between tutorials… yet still struggle to write simple code on their own. It's not because they’re not trying - their approach isn’t working. Here’s what slows most people down: • focusing on syntax instead of understanding (they can write code, but don’t know why it works) • watching instead of practicing (it feels productive, but no real skill is built) • no feedback or direction (so the same mistakes keep repeating) That’s why this bootcamp is different We don’t just teach you what to code - we teach you how to think like a developer. • break down problems step-by-step • write, test, and improve your code • use real tools developers actually work with Because knowing about coding is not the same as being able to code The difference shows when you can sit down, face a problem, and solve it -without relying on a tutorial. In simple terms: Direction beats information. You don’t need more tutorials - you need structure What has actually been your biggest challenge so far? 1️⃣ Understanding 2️⃣ Consistency 3️⃣ Where to start Drop your number below 👇 #GEANCOCommunityCenter #DigitalSkills #CodingBootcamp #TechCareerGrowth #StudentsInTech

The resources that quietly built my tech foundation When I started learning tech, I didn’t have everything figured out. I didn’t know the best roadmap. I didn’t know what tools were “perfect.” I just started with what I could find and stayed consistent. Looking back, a few platforms really shaped my foundation. One of the first places I learned HTML from was The Net Ninja (https://www.youtube.com/NetNinja) simple, structured, and easy to follow, especially as a beginner. I also spent a lot of time learning from Code with Mosh: (https://lnkd.in/e4jKa5Ex.) His explanations helped me understand not just what to do, but why it works. And of course, W3Schools (https://www.w3schools.com) was always there when I needed quick references or to test things out. Honestly… It’s not always about having the “best” resource. It’s about: Showing up consistently Practicing what you learn Going with the flow, even when things don’t make sense And actually building with what you learn Because you can watch tutorials all day, but growth really happens when you apply. Even now, I still go back to the basics sometimes. Learning in tech is not a straight line, it’s a continuous process. If you’re just starting out, don’t overthink it. Pick a resource. Stay consistent. Build. That’s what really makes the difference. What resources helped you when you were starting out? #tech #softwaredevelopment #webdevelopment #learningtocode #techjourney #developers #buildinpublic

The hardest part of learning to code isn't the syntax. It's the moment you get stuck at 11pm with no one to ask. That's the problem with most online learning. You're on your own. You watch, you pause, you rewatch, you give up. At Codeworks, learning happens live, which means when you're stuck, someone's actually there. An instructor who can walk you through it. Classmates who've hit the same wall. A cohort that moves together, gets frustrated together, and figures it out together. Because the fastest way to learn code isn't watching someone else do it. It's building, breaking things, asking questions in real time, and solving problems as a team. That's what we mean when we say live learning. Not a Zoom lecture. Not a pre-recorded module. An actual room, online, yes, but real, where progress happens because people show up for each other. If you've tried learning to code and felt like you were falling behind alone, this is what was missing. Learn it live. Learn it properly. 🔗 Book a Call with Admissions: https://lnkd.in/eXMySYfT #LearnToCode #Codeworks #LiveLearning #CodingBootcamp #FutureInTech #LearnOnline #WebDevelopment #TechCareer #OnlineBootcamp #DevelopingFreedom

Everyone is learning how to code. Very few are actually building. That’s the gap no one talks about. You can finish courses, watch tutorials, and understand concepts… But when it’s time to create something real — most students freeze. Because learning gives you knowledge. But building requires thinking. Thinking about: → What problem am I solving? → How do I structure this? → What should I build first? This shift — from learner to builder — is where real growth happens. At CodingNovas, we focus on that shift. We don’t just teach you how to code. We train you to think, plan, and build like a real developer. 💡 Work on real-world problems 💡 Learn how projects actually come together 💡 Build confidence by doing, not just watching Because in the end… Your skills are proven by what you can build, not what you’ve learned. If you’re ready to move beyond tutorials and start building for real— 🚀 Follow CodingNovas and start your builder journey. #CodingNovas #LearnToCode #BuildInPublic #Developers #StudentGrowth #TechCareers #LearningJourney https://lnkd.in/gaHdSgNz

Day 5 of Mentorship for Acceleration LearningChallenge Nobody really tells you when you start coding thatThe code you write is not for the computer. The computer doesn't care. It will run anything you give it as long as it works. Ugly code, messy code, code with random variable names like x, y, z . It doesn't care. The code is for the next person who reads it. Sometimes that next person is you, three weeks later, completely confused about what you wrote. I looked back at something I wrote two weeks ago and genuinely could not tell what I was trying to do. Same person, same brain, completely lost. That's when it hit me. Writing code that works is one skill. Writing code that makes sense to a human is a completely different skill. And the second one matters more than people think. A #variable named x and a variable named userAge do the exact same job. But one of them tells a story and the other one tells nothing. Small thing. But it changes everything about how you write. Mentorship for Acceleration #FrontendDevelopment #30DaysChallenge #LearningInPublic #M4ACELearningChallenge #WebDevelopment

Day 11 of 100 days. One thing I’ve noticed while teaching my students… They understand a concept today - but forget it tomorrow. It's what I’ve experienced myself too. The challenge: Forgetting what you learn 👉 What I advised my students (and practice myself): • Don’t just learn - apply immediately • Build something small with that concept • Revisit it the next day Learning sticks when you use it. If you’re watching tutorials endlessly without building… that might be the problem. Have you experienced this? Share it in the comments. #FrontendDevelopment #100DaysOfSolvingCodingProblems #WebDevelopment #CodingTips #CodeSistency #LearnByBuilding #LearnByApplication

Tutorial Hell is Real — And It’s Slowing You Down “If you’re always watching and never building, you’re stuck.” It feels like progress: You complete another course You watch another tutorial You understand everything while watching But when it’s time to build something on your own… 👉 You don’t know where to start. That’s tutorial hell. 🔁 What is Tutorial Hell? It’s a cycle: Watch → Understand → Feel confident Try to build → Get stuck Go back to another tutorial 👉 Repeat. You’re learning… but not progressing. ⚠️ Why This Happens Tutorials are designed to be: Structured Step-by-step Easy to follow But real-world development is: Unstructured Uncertain Full of decisions 👉 Tutorials guide you. Reality tests you. 🧠 The Passive Learning Trap When you only watch: You recognize patterns But don’t practice thinking 👉 Your brain says, “I know this.” But your hands say, “I can’t build this.” 🚀 The Shift You Need From: 👉 Watching more To: 👉 Building more 💡 A Better Learning Approach 1. Learn → Apply Immediately After a tutorial, build something small on your own. 2. Break the Fear of Blank Screen Start simple. Even a basic project is progress. 3. Get Stuck on Purpose Struggling is part of learning. 4. Limit Tutorials Use them as support, not a dependency. ❌ Common Mistakes Starting multiple courses at once Copy-pasting code without understanding Avoiding independent projects Waiting to “feel ready” 👉 You’ll never feel 100% ready. 📈 What Real Learning Looks Like You try You fail You debug You improve 👉 That’s where growth happens. 🎯 Final Thought 👉 Tutorials don’t make you a developer. Building does. So next time you finish a tutorial, don’t start another one. Start a project. Even if it’s messy. Even if it’s small. Ask yourself honestly: Are you learning… or just watching? Let’s discuss. What was the first project you built on your own? #Learning #TutorialHell #Programming #BuildInPublic #TechGrowth #toufiqtalks #tufeculislam

“I’ve completed 12 courses… but I still can’t build anything.” That’s what a student told me last week. He wasn’t lazy. He wasn’t “bad at coding.” In fact, he had: ✔ Certificates from multiple platforms ✔ Notes filled with concepts ✔ Hours of tutorials completed But when I asked him to build a simple project… He froze. So I asked him one question: “How many projects have you built without following a tutorial?” Silence. This is where most beginners get stuck. They think: “Once I finish one more course, I’ll be ready.” But that moment never comes. Because you don’t become ready by watching. You become ready by building. So we changed one thing. Instead of starting another course, I told him to build a small project — on his own. No step-by-step guidance. No copy-paste. Just Google, errors, and persistence. The first day? Confusion. The second day? Frustration. The third day? He figured things out. That’s when it clicked for him: “This is the first time I actually feel like I’m learning.” At CodingNovas Academy, this is exactly what we focus on: ✔ Less watching, more building ✔ Real-world projects ✔ Learning through doing, not consuming Because at the end of the day— "If you’re not building, you’re not learning." If you’re learning to code right now, be honest: Are you building… or just watching? #CodingNovas #LearnToCode #DeveloperJourney #Programming #WebDevelopment #CareerGrowth #Students #CodingLife #BuildInPublic #TechCareers #SkillBasedLearning #FutureDevelopers https://lnkd.in/gaHdSgNz

🚫 12 courses complete karke bhi agar banda kuch bana nahi pa raha… toh problem courses me nahi hai. Problem ye hai ki tum sirf dekh rahe ho, kar nahi rahe. Sach thoda harsh hai — Coding YouTube se nahi aati, Coding screen pe struggle karke aati hai. Maine itne students dekhe hain — Notes full, certificates full… par jab bolta hu “ek project bana ke dikhao” → silence. Isliye hum CodingNovas me ek simple rule follow karte hain: 👉 Pehle banao, phir seekho — not the other way around. Messy code likho. Error aayega. Google karoge. Tab actual learning hogi. Agar tum abhi bhi sirf course pe course kar rahe ho… toh seedha bol raha hu — 👉 Tum time waste kar rahe ho. Ab decide karo: Viewer rehna hai ya Builder banna hai? #CodingNovas #BuildInPublic #NoBS #RealLearning #Developers

Hard truth. Most people are not stuck because of bad resources. They’re stuck because they’re inconsistent. They start learning… Then stop. They get excited… Then disappear. They make plans… But never execute. This is why others move ahead. Not because they are smarter. But because they show up daily. In tech, consistency beats everything. Skills don’t grow overnight. They compound. Resources: Full Stack: CodeWithHarry https://lnkd.in/dr3TBu9s Apna College https://lnkd.in/djWs4ewP DSA: Love Babbar https://lnkd.in/d9WnbCum Free Courses: freeCodeCamp https://lnkd.in/ddd3C48 Question: Be honest — are you consistent right now? #Discipline #Consistency #LearnToCode #ProgrammingJourney #DeveloperMindset #SelfImprovement #TechSkills #GrowthMindset #Connexode