{
  "id": 2847496,
  "title": "When Learning to Code Becomes a Loop: Why I’m Choosing to Build",
  "url": "https://urgent.news/2026/08/23/when-learning-to-code-becomes-a-loop-why-im-choosing-to-build",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-08-23T18:50:05.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/goldheart/when-learning-to-code-becomes-a-loop-why-im-choosing-to-build-207a"
  },
  "original_language": "en",
  "account": "When first learning to code, it can feel like you're constantly gaining knowledge, but not gaining the hands-on experience you need to truly build things. Tutorials, courses, and resources are great for understanding concepts, but they don't always translate to real-world application. There's a gap between knowing how something works and knowing how to use it when staring at a blank editor.\n\nMany beginners get caught in this loop, constantly consuming information but building very little. They start a project, become frustrated, or push it aside in favor of learning something else. Eventually, they may step away from coding for a while, thinking they need a break or a new foundation of knowledge before they can start building.\n\nBut the solution isn't to wait until you feel completely ready to start building. That trap can keep you from ever starting at all. The key is to start small and finish projects, even if they're simple. Each completed project exposes you to new problems that tutorials can't fully prepare you for. You'll make mistakes, search for solutions, read documentation, and learn through trial and error. This experience is what truly deepens your understanding and skills as a developer.\n\nThe author realized this after completing a small Frontend Mentor challenge: a Testimonials Grid project. Finishing it was a big victory because they actually started something and saw it through to completion. That small achievement reminded them of a crucial truth: becoming better at development comes from developing, not just learning. Every project provides unique challenges and learning opportunities that tutorials alone can't offer.\n\nNow, the author is changing their approach to learning. Instead of waiting to learn everything before starting to build, they're focusing on starting to build right away. Tutorials and courses will still be a part of their learning, but they want projects to be the center of their development journey. They'll make mistakes, get stuck, try new things, and break things. But through this process of building, getting stuck, learning, and fixing, they'll gain the real-world experience they need to become a more proficient developer. And they're committed to documenting their journey, not because they have all the answers, but because they're still learning and figuring things out. The important thing now is to move forward, one project at a time.",
  "summary": "There was a period when I felt like I was making progress as a developer.I was watching tutorials. Taking courses. Learning new concepts. Saving resources. Watching someone build something and thinking, “Okay, I understand this now.” Then I would move on to the next thing. HTML? Done. CSS? I understand it. JavaScript? I know the basics. React? Let me learn that next. And then another tutorial…",
  "key_points": [
    "Beginners often get stuck in a loop of learning without building.",
    "Small, completed projects expose new problems tutorials can't prepare for.",
    "The author now focuses on building projects to gain real-world experience."
  ],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}