Keep game-development notes usable

A project note should connect a problem with a decision and an observed result. Write down the input sequence, build conditions and the change made.

Return to the note after a break and try to reproduce the result. Add missing assumptions so the document becomes a practical tool for the next session.

Continue the study

Work through a small code example, make one deliberate change and record the effect. The reading links below connect this exercise with animation, input and retro game design.