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…
Luckily when my dad came home he explained that we actually had GW-Basic on the computer (an IBM XT my dad had bought second hand from a friend's dad who was IN computers). That's where it all started. My dad could keep up for a bit but soon I had to rely on whatever the local library offered, and later a floppy disk that somehow made its way to me (copy by copy) full of useful TXT files and examples. Oh internet where were you.
So I feel a bit reserved towards the 'YOUR SON DOES NOT WANT TO LEARN TO CODE' screams that seem only based on very, very little context. But I do agree with the general advise, best to not jump to conclusions and go by their (the kids) pace.