ideas for future improvements

[wikfeldt]

here we add all ideas and considerations for how the bootcamp can be improved in future iterations

[wikfeldt]

• include a preparatory session where we help participants install and configure all tools

[code4yonglei]

most questions from windows users about conda and git bash.
we can have two parallel sessions: one for mac users and the other one for windows users.

[wikfeldt]

Possible long-term plan: we create a single sphinx lesson with all content. Each lesson in separate TOC-section

• shell-intro should probably be taught in one piece at the beginning, and ported from SWC format to sphinx
• consider using a more gentle python introduction, perhaps from SWC python lesson
• which python episodes to include from python-for-scicomp should be reconsidered. Possibly include python content from elsewhere or write new content
• coderefinery lessons stay the way they are

[wikfeldt]

more ideas after discussion with Martin:

• create a few learning paths based on learner background:
  • total beginners - include SWC "plotting and programming in python"
  • coming from different languages - include quick crash course in python syntax
  • consider new topics, e.g. SWC "Using Databases and SQL" and https://coderefinery.github.io/github-without-command-line/
• pre-record videos with the theory and demonstrations, so participants can skip what they already know and focus on new knowledge
• keep it very modular
• consider using ICE for homogenous environment for all participants
• if letting learners use own computers, include installation troubleshooting sessions ahead of bootcamp
• commend from learner: "valuable to see how Python can be used", even if one doesn't really learn it during bootcamp. -> Add a learning objective on this

[code4yonglei]

• recommend to use "lesson" for one material page, e.g. shell-intro, python-for-scicomp, git-intro etc
• each section of a lesson is an "episode"

[wikfeldt]

consider whether to talk about object orientation vs functional approach