[gchallen]

Thanks for sharing! This is really cool. I maintain my own learn-to-program site, so I have a sense of how much work this is.

One interactive component that we use heavily that might interest you for futurecoder is what we call an interactive walkthrough: https://www.learncs.online/best#interactive-walkthroughs. It's like a video but preserving the interactive nature of a playground. Students really like them, and enjoy the opportunity to hear multiple explanations for the same concept when they're stuck. (We're working on popping this out for external use, and have a library in the works that you may be able to integrate with a bit of work.)

I have no idea what your educational background is, but if you ever want a stable position that supports your educational innovation, consider applying for a teaching faculty job: https://go.cs.illinois.edu/teaching-faculty-hiring. (Currently our openings require a Masters degree.) We need more creators in computer science education.

[alexmojaki]

> One interactive component that we use heavily that might interest you for futurecoder is what we call an interactive walkthrough: https://www.learncs.online/best#interactive-walkthroughs. It's like a video but preserving the interactive nature of a playground. Students really like them, and enjoy the opportunity to hear multiple explanations for the same concept when they're stuck. (We're working on popping this out for external use, and have a library in the works that you may be able to integrate with a bit of work.)

Awesome! I've only seen one other place doing something similar: https://scrimba.com/

This is definitely better than ordinary videos, and I like the point about multiple explanations. Although I do personally prefer that futurecoder rarely shows/tells without actually forcing users to run code and see for themselves, so they always have to be engaged. Even when they're told the exact code to run, they occasionally get asked to predict what the output will be, to make sure they're paying attention.

> I have no idea what your educational background is, but if you ever want a stable position that supports your educational innovation, consider applying for a teaching faculty job: https://go.cs.illinois.edu/teaching-faculty-hiring. (Currently our openings require a Masters degree.) We need more creators in computer science education.

It'd be great if I could be paid to work on futurecoder or something similar full time, and I've tried finding a way to make that happen before. But now I've just started a dream job at https://ought.org/ (working with AI, not education) and it'd be very hard to compete with that.

I don't have a Masters and I prefer to create things that are infinitely reusable rather than teaching directly. But thanks for the suggestion!

[gchallen]

> Although I do personally prefer that futurecoder rarely shows/tells without actually forcing users to run code and see for themselves, so they always have to be engaged.

Yup. I agree with this approach. However, I think that in some ways this is a weakness of the side-by-side format you're using, since it seems to lean toward more content per example to offset the playground consuming half of the screen area. On https://learncs.online/ we also prefer a "show not tell" approach, but because we're interleaving the text and the playgrounds, sometimes the text between two playgrounds is extremely minimal: "Let's see what happens when we try it another way."

But there is something nice about the side-by-side format.

> Awesome! I've only seen one other place doing something similar: https://scrimba.com/

Yeah, Scrimba makes it weirdly hard to figure out what's going on, given that some of their early examples just have slides popping up everywhere and no actual text editing. I had to fast forward a bit to get to an editing example. And while I think their integration with (I assume) embedded VSCode is really cool, there's a bit of that "seated at the controls of a 747" feeling immediately with their courses, which I think can be a bit frightening for beginners. We like to keep things really compact for a while, and don't have students work in a full IDE until halfway through the semester. (This also avoids the problem with too much IDE help too early, which you referenced in another comment.)

[gchallen]

> I prefer to create things that are infinitely reusable rather than teaching directly.

Also: teaching directly can be done by creating things that are infinitely reusable :-).