Finished the tutorial. Now make your own game.

Begin with something you can explain

Open a small project you have permission to modify. Explain how the player moves, how the game decides success, and how restart works. If you cannot explain one part, inspect that part before adding features.

You are looking for a manageable place to make a decision. Rebuilding a large course project from memory is a tough opening move if you already feel stuck.

Change a rule that changes a choice

In a catching game, make carried objects slow the basket. In a platformer, make a light open a route rather than merely increase score. In a block puzzle, let a cleared row alter the next piece.

Before coding, write your prediction: “Players will sometimes deliver early instead of carrying the maximum.” After playing, compare the prediction with what happened. You have now made and tested a design decision.

Ask for help on the missing piece

A tutorial, documentation page, or assistant can explain the part you need. Try applying the explanation yourself, then explain the change in your own words. If the code remains a mystery, ask a smaller question.

A brief to make your own

I understand how this catch game moves and scores. I want carrying more parcels to reduce speed until delivery. Help me locate the state and movement code involved. Explain the smallest change, then let me test it before adding anything else.

Close the loop

Stop when this version is complete. A menu redesign is a very tempting way to avoid showing someone the mechanic. It is also still a menu redesign.

1. Make the changed rule visible to the player.
2. Check success, failure, and restart with the new state.
3. Let another person play without telling them your prediction.
4. Write a short note about what you changed and what you learned.

Make the next project slightly more yours

Keep one thing familiar and change another. You might keep the movement code while designing a new level, or keep the board while changing the scoring rule. Gradually you will have more parts you understand and fewer blank spaces.

The goal is not to stop using references. Experienced developers use them too. The goal is to know which question you are asking and to make the decisions that turn the answer into your game.