Is it normal to understand coding exercises but still feel unable to build projects?

Think of exercises as practice for the problem-solving part of programming, not as a test of how much Python syntax you can memorize. Try solving a problem in plain language first, divide it into functions or steps, and then implement each piece. When you get stuck, use documentation, search results, example code, or AI as a tutor rather than blindly copying a complete solution. Repetition and reuse will gradually make common patterns feel automatic.

Confidence often lags behind ability, and it may never become a permanent feeling. Even experienced programmers sometimes feel lost when they enter an unfamiliar codebase or technology. Building projects, reviewing your mistakes, and explaining concepts to someone else can make your progress more visible. Don’t measure yourself by whether you remember everything from memory; measure whether you can understand a problem, make progress, investigate obstacles, and eventually produce working code.

The best way to gain confidence is to start building small things before you feel ready. Choose something useful or entertaining, such as a command-line to-do list, a calendar generator, a text adventure, or a small tool for a problem in your daily life. Don’t try to make it impressive or perfect. Get a basic version working, then add one feature at a time. Finishing a modest project teaches you much more about planning and debugging than endlessly completing isolated exercises.

Yes, this is completely normal. Exercises give you a clearly defined problem, constraints, and expected outcome, while a real project starts with a vague idea and requires you to decide what to build and how to organize it. Keep practicing the fundamentals, especially breaking a large problem into smaller pieces. Forgetting syntax is fine—experienced developers look things up constantly. The important skill is understanding the concepts and knowing how to find or verify the details you need.