I’m going to be delivering an online intro to programming session to a non-technical crowd who will be “following along at home”. Because it’s online, I can’t provide them with machines that are already set up with an appropriate development environment.

I’m familiar with Linuxes and BSDs but honestly have no idea how to get set up with programming stuff on Windows or macOS which presumably most of these people will use, so I need something I can easily instruct them on how to install, and has good cross-platform support so that a basic programming lesson will work on whatever OS the attendees are running. Remember they are non-technical so may need more guidance on installation, so it should be something that is easy to explain.

My ideas:

  • C: surely every OS comes with a C compiler pre-installed? I know C code is more platform-specific, but for basic “intro to programming” programs it should be pretty much the same. I think it’s a better language for teaching as you can teach them more about how the computer actually works, and can introduce them to concepts about memory and types that can be obscured by more high-level languages.

  • Python: popular for teaching programming, for the reasons above I’d prefer not to use Python because using e.g. C allows me to teach them more about how the computer works. You could code in Python and never mention types for instance. Rmemeber this is only an intro session so we’re not doing a full course. But Python is probably easy to install on a lot of OSes? And of course easy to program in too.

  • Java: good cross-platform support, allows for teaching about types. Maybe a good compromise between the benefits outlined above for C and Python?

Any opinions?

  • Sunsofold@lemmings.world
    2·
    22 hours ago

    Depends a bit on how much depth and which topics you want to hit. Scratch is easy to grasp and won’t require any real effort to set up, but may make adults feel like they’re being condescended to with its cartoony aesthetic, and might be a bit limited in how impressive you can make your demo. Python would require a bit of ‘teacher’s planning time’ to set up an easy workspace in Google’s collab tools and design a lesson, but could be used to show more depth if the students are the type to want/accept that depth, but don’t mistake interest for readiness.

    Time might also be important to consider as well. If you have only the one session to cram things into, it might not be a great idea to go deep, and definitely would be asking for trouble to try to install anything on all those machines. Non-technical people have a knack for finding the holes in your plan or taking far longer to do something that requires them to act individually, which leaves you scrambling to try to play remote tech support for the 5-50% who need it while the people who ‘did it in one’ get bored.

    And first things last, Murphy’s Law always applies to presentations. Just ask anyone at defcon. Even for people who are so tech-y they are teaching other tech people about tech, the demo might work 37 times the morning before your presentation, but it will fail on the 38th because that’s when you’re in front of the audience. Minimize your attack surface. When you are limited to one session, leaving them with a good, inspiring message that makes them want to keep learning is better than trying to info dump.

    Good luck.