One huge card too heavy to lift, snapped into four small cards the buddy can pick up and carry one at a time.
Take one big job you don't know how to start, and chop it into small jobs you DO know how to start. That's it - that's the whole trick (grown-ups call it 'decomposition,' a fancy word for a simple idea). 'Make a game' feels huge and scary. But 'draw a spaceship', 'move it left and right', 'count the points' are three small jobs you could start right now. Every big program you'll ever see was built this way - nobody writes a whole game at once, they write lots of small pieces that add up to one.
Big job: Tidy my room
1. Put dirty clothes in the basket
2. Put books on the shelf
3. Put toys in the box
4. Make the bed'Tidy my room' is a feeling. The four small jobs underneath it are things you can actually start, finish, and tick off - and you can do them one at a time without holding the whole room in your head.
Mistake 1: chopping into pieces that are still too big, like 'do the hard part'. If you can't picture starting it, chop again. Mistake 2: trying to hold the whole big job in your head at once and freezing. Nobody can. That's not a you problem, it's a size problem.
In the app this lesson continues with the animated explanation, spoken aloud, and then the practice: Four of these cards are small jobs you could actually start today. One is the big job they add up to. Tap the four small jobs. The editor runs your child’s real code and checks the result, with their coding buddy reacting to what they wrote.
Try it free