Understand that you're not going to finish what you start. Do things that are fun. Keep a notebook of ideas. Talk about plans and what you want do. Spend time with him. Even if almost none if it ever makes it into code, the imagination part will be going wild. Look at what he's really doing. He doesn't want to CODE. He wants to make a game. Like every kid. Emphasize the creative part just like he wants. Do things on…
> He doesn't want to CODE. He wants to make a game. Like every kid. [emphasis mine] Well, I as a child (say: 6-8 old) was really rather thinking deeply how a suitable way (what programmers would call "data structures" and "programming abstractions", "design of a programming languages" - but of course on a child's level) might look like so that the computer can "understand" and precisely execute my game ideas; my game…
And I was thinking how does code translate into something like red alert. I didn't have anyone to guide me to fill in the dots at the point though and it was just before internet was common everywhere and before google was a household name in England at least to me.