Post #46857

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.