@futurebird Another problem is explaining to them that errors are good and that the compiler is their friend, as you already explained. It's not easy with C, for instance, where the compiler spits very obscure error messages.

Good luck!

@futurebird I try to separate clearly the moments when they code and the moments when I explain stuff. When I explain, they have to listen (not look at their computers). They naturally tend to not interrupt with “it doesn't work” comments, and usually ask interesting questions. For this to work, I always promise that I will share with them the code I typed I front of them (for that, I use my institution's platform).