The one thing that helped a lot, was teaching HTML. How td is child of tr and sister to another td, and it has a child of h1, or how things have properties bord

The one thing that helped a lot, was teaching HTML. How td is child of tr and sister to another td, and it has a child of h1, or how things have properties border=2 and etc. It helped with understanding where does code belong, how the code in the for loop is related to the code above it and etc. I also spend time on things like how to steal someone's cookie, and what is a cookie day 51,52,53 (https://github.com/jackdoe/programming-for-kids#day-52-basics-of-the-internet https://github.com/jackdoe/programming-for-kids#day-52-basic...) and also we spend a lot of time touchtyping, so her thoughts easier to be expressed through the keyboard. Also as the talk also mentions, we spend a lot of time reading code, https://github.com/jackdoe/programming-for-kids#day-72-basics-of-basics https://github.com/jackdoe/programming-for-kids#day-72-basic... i just print it on paper and we go over it with a pencil. The most difficult lessons are the more abstract ones understanding what the memory holds, and what the variable points to https://github.com/jackdoe/programming-for-kids#day-95-basics-of-basics https://github.com/jackdoe/programming-for-kids#day-95-basic... Also tearing down commodore64 and showing the actual memory address space in physical manner helps, the variable color points to somewhere >here<. We are spending about 50 days now only doing lists and for loops, I write the next day's lesson after the current lesson finishes, and I try to see what she grasps, and what is somewhat interesting and prepare for tomorrow.