Create a reference doc for instructors and trainers to remind folks of tips. Blake has forgotten lots of the SWC training tips.

Examples:

1. Repeat questions from participants so every can hear the question
2. Talk attendees through their problems. Never take the keyboard from them. If you type on the keyboard they aren't learning anything!
3. At the beginning of every lesson, ask for Green stickies for everyone that can hear
4. At the beginning of every lesson, ask for Green stickies for everyone that can see the screens
5. Leave out terms like simple, just, easy :)
6. lots of others I'm sure

The swc-installation-test-2.py test script that SWC provides is confusing for our attendees. We should create a streamlined version specific to our lessons and remove anything superfluous. The stream of 'failed' messages really confuses people (rightfully so).

Examples:

• Test script includes things like Mercurial (we don't use this) which fails the test script (because we don't use it)
• EasyMercurial (fails)
• make fails on some computers (I'm unclear whether that's important or not)

Output from my run

check text/code editor (virtual-editor)...	pass
check web browser (virtual-browser)...	pass
check Git (git)...	pass
check Mercurial (hg)...	fail
check EasyMercurial...	fail
check make...	pass
check PyPI installer (virtual-pypi-installer)...	pass
check Setuptools (setuptools)...	pass
check Nose (nosetests)...	pass
check Nose Python package (nose)...	pass
check py.test...	pass
check pytest Python package (pytest)...	pass
check SQLite 3 (sqlite3)...	pass
check SQLite Python package (sqlite3-python)...	pass
check Python version (python)...	pass
check IPython script (ipython)...	pass
check IPython Python package (IPython)...	pass
check Argparse (argparse)...	pass
check NumPy (numpy)...	pass
check SciPy (scipy)...	pass
check Matplotlib (matplotlib)...	pass
check Pandas (pandas)...	pass```

Needs to be introduced for at least one exercise

Discussion with a few folks. We think it is a good idea to create a gif that illustrate how if and elif works.

Upendra's idea. He plans to show the class some stats about themselves that he coded in a jupyter notebook with python as a way to peak interest for the second day. Seems like running that for every future class is a good idea.

In the 01 python lesson about Python data structures, the information about tuples got split. Will need to merge some cells up (starting with icecream tuple example, etc.)

Need to change any read_table() calls to read_csv(). This is also going to be confusing for the participants.

After Hello World examples in the 01 lesson, a concatenation was included. I don't object to having concatenation earlier, but the following EtherPad exercise refers to greeting. Perhaps that should be moved up to avoid the break-up.