Building

Writing the code is rarely the hard part. Keeping the project small enough to actually finish is.

Three things worth doing:

1. Keep the scope small. A working five-hour project you ship beats an ambitious fifty-hour engine you abandon. Get the core feature done, then expand if you still want to.
2. Build something you'd use. Solving a problem that annoys you, or making a game you want to play, keeps you going far longer than a project you picked because it sounded impressive.
3. Commit often. Push after every session. It backs up your work, and it gives reviewers a clear record of how the project came together.

Build your first project walks through the setup step by step.