CoCalc talk (1 hour)

• 10 minute live demo of cocalc itself

• 10 minute history:

  • online tables on my website at Berkeley (and Hecke)

  • magma & pari online calculators for Harvard class

  • Sage Notebook

  • SageMathCloud

  • CoCalcs

• 15 minute sketch of current architecture

• 5 minutes:

  • getting your software in cocalc

  • using cocalc to make your software and OSS more accessible

• 15 minute interactive demo with audience

Idea from @hal:

Lots of potential here. You could expand this. Ways to make your software more student-friendly. Does not have to be a CoCalc infomercial. Horror stories integrating things into the CoCalc stack. One or two of these. Will be memorable if told with humor.

haskell (packaging system ?) julia gap kernel swirl Stuff that uses

nonstandard toolchain to build esoteric dependencies funky version control (hg, svn) There are things that make software hard to use in any exploratory & collab setting:

console interaction (swirl again) widgets Things that invite students to fall into traps or get frustrated:

ballooning memory allocation without warning or any other use of resources that doesn't play well with others - like jupyter notebooks running and running, which is why we put in the halt button on ours crap error messages or just crashing on failure going away for minutes at a time - am I working hard or stuck no safety rails so a student can call the app with parameters that blow it up inexplicably Teacher can make life easier for self (this could make some good conversations around the event):

write homework that is easy to grade in online setting don't create materials deeply tied to teaching framework UI details - these change a lot - or isolate in separate short content that's easy to update what sort of sample problems are more fun in collaborative setting?