Tutorial Assistants (TAs) are volunteers that help students learn by removing roadblocks from their learning such as setup issues, or by offering one on one help during exercises where's it's impractical for an instructor to answer questions from everyone in the tutorial.
As a TA your primary purpose is to help students. Your secondary purpose may be to learn from the instructor, but don't let it interfere with your primary purpose. Don't bring a laptop, take a spot at a table, or take a handout. Do listen and learn when you're not helping.
Help with diagnosing platform-specific problems on a platform the instructor doesn't know or use.
Give general Python help with exercises for students that are relatively new to Python.
Give subject-specific help with exercises where you have expertise in the tools or concepts being taught.
Try to be visible to students who need help, but invisible to the instructor and not distract from their teaching.
By default, don't ask questions and don't correct the instructor, unless they've said they want that. They'd love to hear your feedback after the tutorial, but during a tutorial it may interefere with their teaching.
Ask the instructor how else you can help.
Enjoy your experience! Assisting in a tutorial is a very rewarding experience, helping participants get unstuck, seeing their ah-hah moments, and getting to know them. In large tutorials teachers can't make connections with very many students - but you can with a few.
Help people new to PyCon feel welcome. Reach out to wallflowers during breaks.
Join us for the catered snacks and lunch on us.
Add an entry to the table below. Indicate the slots for which you're available, and list your expertise areas so we know where you're best suited to help. This information will be shared with Instructors who are looking for more TAs.
Show up at the Tutorial Preparation Sessions to meet instructors, get last minute assignments to assist in tutorials, and help tutorial participants with laptop setup.
Show up during the Tutorial days to offer ad hoc Tutorial Support.
|Wed a.m.||Wed p.m.||Thu a.m.||Thu p.m.||Contact Info||Expertise and Notes|
|email@example.com||10 years using Python, 6 with numpy, some Django|
|yes||yes||no||no||tarek at ziade.org||Python, Packaging issues, Linux|
|no||yes||no||yes||kesavkolla at gmail.com||Tornado, AsyncMongo, Pyramid, Virtualenv|
|no||yes||yes||yes||benjamininwarfield at just-another.net||Various Web, Infrastructure (ops), packaging, messaging, *nix, testing|
|no||no||no||yes||hodgestar at gmail.com||broadish Python experience since ~2.4|
|no||no||yes||yes||senthil at uthcode||Python, Networking Libraries, Standard Library|
|yes||yes||yes||yes||roydebox at gmail.com||8 years using Python, experiences in PyPy, Cython, gevent, server dev, machine learning, NLP, Search.|
|yes||no||yes||yes||jspies at gmail.com||6 years using Python, web frameworks, statistics|
Wait to be contacted by Instructors. They may ask questions to be sure you'd be a good match for their tutorial.
If you don't hear ahead of time, show up at the Tutorial Support sessions or on Tutorial Days to help out.
If you get an assignment, edit your availability in the table above or remove your name entirely.