How Coding Practice Develops Technical Skills

A few years ago, I mentored a young professional eager to transition into data science. He had enrolled in multiple bootcamps, downloaded several Jupyter notebooks, and even joined several learning communities. But after months, his progress was minimal. When I asked what her daily routine looked like, she replied, “I mostly read through the codes and run the notebooks to see what happens.” That was the moment I realized many people “learn” programming without ever truly programming. The Common Mistake Most beginners consume content passively, watching tutorials, scrolling through code samples, or running prepared scripts. It feels productive, but it’s deceptive. You’re observing code, not internalizing it. You’re copying others’ logic, not building your own problem-solving muscles. Programming is a muscle skill, not a memory skill. And like any muscle, it only grows through deliberate, consistent practice. The Framework That Works I always teach beginners this simple progression: Watch → Type → Tweak → Build → Repeat. 1. Watch: Understand what the code is meant to do. 2. Type: Don’t just run it. Type every line yourself in your IDE (VS Code, RStudio, or Jupyter). 3. Tweak: Change something intentionally, a function name, variable, or dataset and see what breaks. That’s where learning lives. 4. Build: Start a small project that solves your problem, no matter how simple. 5. Repeat: Two hours daily is better than ten hours once a week. Consistency transforms confusion into confidence. Why It Matters for Data Scientists and Global Health Professionals In global health and development, programming isn’t just about code, it’s about turning messy data into meaningful action. Whether you’re analyzing HIV outcomes, forecasting disease trends, or visualizing impact indicators, your ability to manipulate data directly shapes the insight you can produce. When you code actively, typing, testing, and iterating, you’re not just learning syntax. You’re training your mind to think logically, troubleshoot systematically, and approach public health problems like a true data scientist. Your Turn Ask yourself: Are you reading code, or are you writing it? Are you building the confidence to solve problems — or just watching others do it? Start small. Code daily. Break things. Fix them. That’s how you grow from learning programming to thinking like a programmer. #DataScience #Programming #AIForGood #AnalyticsForImpact #SIAnalytics #GDIN #GlobalHealth

Why Practice Makes a Better UI Engineer Let’s be honest: Auto-generated code looks clean—until you have to debug it. That’s where reality hits. 👉 True skill comes not from watching code appear, but from writing, rewriting, and fixing it yourself. Here’s why practice beats shortcuts: 1️⃣ Debugging confidence → You know where to look when errors pop up. 2️⃣ Design control → You can tweak pixel-perfect details AI can’t. 3️⃣ Framework fluency → You naturally learn idioms and best practices. 4️⃣ Ownership → You trust your code because you built it. Think of it like driving. You wouldn’t trust a driver who only knows “auto-pilot.” Same with engineering—you need hands-on experience to steer. 💡 Want to be a better UI engineer? Practice, break things, fix them, repeat. And if you’re serious about sharpening your frontend chops, check out https://iocombats.com – real-world UI challenges where you code, not just copy. 🚀 That’s how confidence is built.

To prepare for technical interviews at FAANG (Google, Apple, Microsoft, Amazon, and Meta), here's strategy: To prepare for technical interviews, focus on solving coding problems regularly. 1. Practice Coding Every Day:   - Try solving at least one medium or two easy-level coding questions daily.   - Do it on your own without help, but if you're stuck for over an hour, look for hints or solutions.   - Make notes of what you missed while solving and revise them often. 2. Focus on Concepts:   - Spend time understanding the concepts behind each problem you solve.   - Revise your notes and practice problems regularly to strengthen your understanding. 3. System and Design Studies:   - Aim to prepare at least one system and one object-oriented design case study each week. 4. Stay Consistent:   - Consistency is key. Stick to your daily coding practice routine.   - Use the Pomodoro Technique: plan 25 minutes of focused preparation followed by a 5-minute break, and repeat. 5. Include Behavioral Interviews:   - Don't overlook behavioral interviews. Give them equal importance in your preparation. For effective use of LeetCode: 1. Quality Over Quantity:   - Focus on solving quality problems rather than just solving many.   - Follow a roadmap of quality problems, like the 100 Days to GAMAM plan. 2. Use Curated Lists:   - Solve LeetCode's curated list of top interview questions, including the top 100 liked questions. 3. Practice Weak Areas:   - Identify your weak areas and practice questions specifically in those topics.   - Sort problems by "Acceptance" after choosing a difficulty level for better chances of success. 4. Gradual Progression:   - If you're a beginner, start with easy-level problems and gradually move to medium and hard levels.   - Aim to solve a target number of problems at each level. 5. Utilize Resources:   - Check out multiple solutions to problems and understand their time and space complexities.   - Take notes on missed concepts and revise them regularly. 6. Challenge Yourself:   - Once you're comfortable with practice, try daily challenges and participate in contests.   - Track your progress and consistency using LeetCode's features, like session management and submission graphs. LeetCode Practice:   - Solve LeetCode problems daily for 1-2 hours.   - Focus on quality over quantity.   - Start with easy problems if you're a beginner.   - Practice topics where you feel weak.   - Check out multiple solutions for each problem.   - Aim for a balanced number of easy, medium, and hard problems. Problem Solving Techniques:   - Don't spend more than 45-60 minutes on a problem.   - If stuck, check hints or solutions, but try to understand them fully.   - Take notes on missed concepts and solutions.   - Revise problems frequently, following a schedule based on Ebbinghaus's Forgetting Curve. consistent practice, understanding concepts, and targeted preparation will help you ace your technical interviews! Follow Vikram Gaur #faang

If your goal is to truly learn coding, consider turning off tools like GitHub Copilot—at least in the beginning. Yes, you read it right. Real learning happens when your mind is fully engaged in problem-solving. When you struggle with syntax, logic, and debugging, your brain opens up, it stretches and forces you to think. That mental effort is good, i have experienced it myself. it’s the process of learning. When Copilot is constantly suggesting solutions, ww immediately want to accept code without fully understanding how or why it works. don't you think? Over time, this can weaken your ability to think critically, design logic independently, and troubleshoot issues effectively. This is especially important for testers or beginners who are transitioning into coding or experienced people who wants to learn automation testing. At this stage, building strong fundamentals—understanding control flow, edge cases, and debugging techniques—is more important. AI tools like Copilot are powerful, we all know but they should be used ( once you know coding concepts) First, develop the habit of: -writing code by your hands,full line of code -Breaking down problems on your own -Writing logic step by step -debugging without hints -Understanding errors Once you build that foundation, AI can become a helpful assistant for sure, I believe. Use AI to enhance your skills—not to replace your thinking. don't be fully dependent on such tools. Are you usinggithub co-pilot autosuggestions blindly ? Or, do you first analyse the code before using it? lets discuss. #LearnToCode #DeveloperMindset #ProblemSolving #SoftwareTesting #Upskilling #GitHubCopilot #SDET

🤔 Why does it feel like I’m stuck after watching hours of coding tutorials? Here's the hard truth: Watching someone code is like watching someone swim. You'll never learn to float by sitting on the beach. 🧠 You don’t become a better programmer by watching. You become one by doing. → If you’re learning web development, are you building websites from scratch? → If you’re learning data science, are you playing with datasets? → If you’re learning software engineering, are you coding small tools? → If you’re learning the fundamentals, are you coding basic challenges? Not sure where to start? Here are some great platforms to find challenges for any programming path:  👩🏾💻LeetCode - For algorithm and coding challenges. https://leetcode.com/ 👩🏾💻 HackerRank - Solve problems and build domain skills. https://lnkd.in/es9Qb3Gc 👩🏾💻 freeCodeCamp - Build projects while learning. https://lnkd.in/euXPmkfx 👩🏾💻Frontend Mentor - Real-world web development challenges https://lnkd.in/eFH9qud6 👩🏾💻 Kaggle - Explore data science competitions. https://www.kaggle.com/ 👩🏾💻 Exercism - Great for language-specific practice https://exercism.org/ 👩🏾💻 Codewars - Fun, gamified learning. https://www.codewars.com/ 👩🏾💻 Edabit - Short, fun coding challenges. https://edabit.com/ Remember: Active learning is more effective than passive learning. A single hour of writing code teaches more than 10 hours of watching tutorials. Tackle challenges, no matter how small. 𝗖𝗼𝗱𝗲. 𝗠𝗮𝗸𝗲 𝗺𝗶𝘀𝘁𝗮𝗸𝗲𝘀. 𝗙𝗶𝘅 𝘁𝗵𝗲𝗺. 𝗥𝗲𝗽𝗲𝗮𝘁. What small project will you start coding today? 💻 What other coding platforms will you recommend? #Programming #Tech #Growth #LearnWithSofiat

My client passed 8 out of his next 10 technical assessments in just 4 weeks of working together They went from failing every technical assessment, hating and blaming the system… But the truth is: You don't rise to the occasion. You fall to the level of your preparation. So I taught him what I teach all my clients: Don’t cram for interviews, train like an athlete, and practice like a professional. Here’s how I help clients prep for interviews without burning out or waiting until an assessment shows up in their inbox. We build coding prep like a habit stack. Each layer trains a real-world interview skill. 𝟭) 𝗟𝗲𝘃𝗲𝗹 𝟭: 𝗗𝗮𝗶𝗹𝘆 𝗰𝗼𝗱𝗶𝗻𝗴 𝗽𝗿𝗮𝗰𝘁𝗶𝗰𝗲 (𝟯𝟬 𝗺𝗶𝗻𝘀) Daily coding practice on Platforms WHY? To start interview prep for the assessment and live coding rounds 𝟮) 𝗟𝗲𝘃𝗲𝗹 𝟮: 𝗣𝗿𝗮𝗰𝘁𝗶𝗰𝗲 + 𝗽𝘂𝘀𝗵 𝘁𝗼 𝗚𝗶𝘁𝗛𝘂𝗯 Daily coding practice on Platforms + Git, committing progress\ WHY? To retain more information and be able to reflect on your progress 𝟯) 𝗟𝗲𝘃𝗲𝗹 𝟯: 𝗔𝗱𝗱 𝗰𝗹𝗲𝗮𝗿 𝗰𝗼𝗺𝗺𝗶𝘁 𝗺𝗲𝘀𝘀𝗮𝗴𝗲𝘀 Daily coding practice on Platforms + Git, committing progress with good commit messages WHY? To practice clearly communicating to your team with git 𝟰) 𝗟𝗲𝘃𝗲𝗹 𝟰: 𝗧𝗿𝗮𝗰𝗸 𝘁𝗶𝗺𝗲 𝗶𝗻 𝗰𝗼𝗺𝗺𝗶𝘁 𝗺𝗲𝘀𝘀𝗮𝗴𝗲𝘀 Daily coding practice on Platforms + Git, committing progress with good commit messages + Adding time, then adding how long it took in your commit message WHY? To practice like the interview (assessment or live coding) with a little more nervousness, so you can crush the interviews 𝟱) 𝗟𝗲𝘃𝗲𝗹 𝟱: 𝗧𝗮𝗹𝗸 𝗼𝘂𝘁 𝗹𝗼𝘂𝗱 𝘄𝗵𝗶𝗹𝗲 𝘀𝗼𝗹𝘃𝗶𝗻𝗴 Daily coding practice on Platforms + Git committing progress with good commit messages + Adding time, then adding how long it took in your commit message + Talking aloud WHY? To practice like the interview (live coding, case study, system design) by communicating your actions and reasoning, so your practice is more like the real thing, and you can crush the interviews 𝟲)𝗟𝗲𝘃𝗲𝗹 𝟲: 𝗦𝗵𝗮𝗿𝗲 𝘄𝗵𝗮𝘁 𝘆𝗼𝘂 𝗹𝗲𝗮𝗿𝗻𝗲𝗱 (𝗮𝘀 𝗰𝗼𝗻𝘁𝗲𝗻𝘁) Daily coding practice on Platforms + Git committing progress with good commit messages + Adding time, then adding how long it took in your commit message + Talking aloud + Creating a mini content WHY? To start building the habit of creating content from your learnings. The easiest way to create content is to document your life This method has helped my clients pass 80 %+ of coding rounds and land roles in data, analytics, and tech. Take a look at what stage you are on, then, when you are consistent, you can move to the next one. Let’s build the habit, not the panic. ♻️ Repost if you found this helpful

This $0.10 index card tripled my coding skills in 30 days: It's called the 3x3 Dopamine Diary. And it works because it's built on neuroscience, not willpower. Like most developers, I used to learn in bursts. I'd get excited about a new technology, study intensely for a week, then gradually lose momentum until I'd forgotten most of what I'd learned. Sound familiar? The problem wasn't my intelligence or even my motivation. It was my approach to learning. That's when I discovered this ridiculously simple but powerful system: Take an index card. Write the days of the month across the top. Down the left side, write these three developer learning habits: 1️⃣ Technical Reading (20 min): Documentation, technical blogs, or books about your stack 2️⃣ Implementation Practice: Apply ONE new technique or pattern you've learned (even something tiny) 3️⃣ Knowledge Sharing: Document one learning or solution (in team wiki, personal notes, or code comments) Each day, check off which habits you completed, then give yourself a score out of 3. Why this works when fancy apps and expensive courses often fail: It taps into your brain's dopamine reward system with immediate, visible progress. Physical tracking creates stronger neural connections than digital The habits are small enough to do even on your busiest days (10-20 minutes total) Documenting what you learn forces deeper understanding and retention What skill would you focus on if you tried the 3x3 Dopamine Diary for 30 days?

𝐖𝐡𝐲 𝐭𝐡𝐞 𝐛𝐞𝐬𝐭 𝐝𝐞𝐯𝐞𝐥𝐨𝐩𝐞𝐫𝐬 𝐈 𝐤𝐧𝐨𝐰 𝐭𝐫𝐞𝐚𝐭 𝐭𝐡𝐞𝐢𝐫 𝐜𝐫𝐚𝐟𝐭 𝐥𝐢𝐤𝐞 𝐦𝐮𝐬𝐢𝐜𝐢𝐚𝐧𝐬 𝐭𝐫𝐞𝐚𝐭 𝐭𝐡𝐞𝐢𝐫 𝐢𝐧𝐬𝐭𝐫𝐮𝐦𝐞𝐧𝐭.🧙🏽♂️ Every musician knows: practice 30 minutes a day. Not performing. Not rehearsing. Just you, your instrument, and the basics. Scales. Breathing. Technique. Over and over. Now look at coding. We write code eight hours a day. But that's not practice. That's performing. Practice means working on a skill outside of production pressure. In music, nobody questions this. In coding, we skip it entirely. That's like improving your vocal range by only singing concerts. In sports it's the same...in martial arts the concept of "Katas" exist for that reason. And "Code katas" do the same! Small, focused exercises. One pattern. One repetition. 15 to 30 minutes. After weeks, you don't just write faster. You think differently. The boring repetition before the concert is what makes the concert possible. The same is true for your codebase. What's your version of "daily practice" in your craft? #ALDITechfluencer #CodeKatas #ContinuousLearning

💻 𝐖𝐚𝐭𝐜𝐡𝐢𝐧𝐠 𝐞𝐧𝐝𝐥𝐞𝐬𝐬 𝐜𝐨𝐝𝐢𝐧𝐠 𝐭𝐮𝐭𝐨𝐫𝐢𝐚𝐥𝐬 𝐰𝐨𝐧’𝐭 𝐦𝐚𝐤𝐞 𝐲𝐨𝐮 𝐚 𝐛𝐞𝐭𝐭𝐞𝐫 𝐝𝐞𝐯𝐞𝐥𝐨𝐩𝐞𝐫. 𝐀𝐜𝐭𝐮𝐚𝐥𝐥𝐲 𝐜𝐨𝐝𝐢𝐧𝐠 𝐰𝐢𝐥𝐥. There’s a term for getting stuck in a cycle of tutorial after tutorial without ever applying what you’ve learned: 𝑻𝒖𝒕𝒐𝒓𝒊𝒂𝒍 𝑷𝒖𝒓𝒈𝒂𝒕𝒐𝒓𝒚. And it’s way too easy to fall into. You know the concepts. You understand the syntax. But when it comes time to build something on your own, you freeze. Why? Because 𝒓𝒆𝒂𝒍 learning happens through application, not observation. 🤔 𝐇𝐨𝐰 𝐝𝐨 𝐲𝐨𝐮 𝐞𝐬𝐜𝐚𝐩𝐞 𝐓𝐮𝐭𝐨𝐫𝐢𝐚𝐥 𝐏𝐮𝐫𝐠𝐚𝐭𝐨𝐫𝐲? ✅ Pick a project that solves a problem you actually have. It doesn’t matter if there’s already a solution—what matters is you building it. ✅ Get comfortable researching. Debugging and troubleshooting are skills you only develop by doing. ✅ Embrace documentation. Docs are your best friend. The sooner you start using them, the faster you'll grow. ✅ Find a community. Whether it’s Dev.to Discord or a local meetup, having people ask for help and share wins with makes a huge difference. Every bug you fix, every problem you debug, every time you struggle through an error message—you’re learning. That’s how you level up. So if you’ve been stuck in tutorial mode, here’s your sign to start building. What’s the first project you’re tackling? And if you want more practical tips to improve your coding skills, hit that follow button. 🚀 #Coding #SoftwareEngineering #LearningToCode #CareerGrowth ----- Side note: I've been working on integrating my interests into my videos more, and I'm so proud of how this video turned out. I hope you enjoy it as much as I did when creating it 😊