• The goal is to expose students to every day situations they'll face as TAs and to provide tools on how to handle them.
• There is no evaluation from the facilitators' side.
• The evaluation should come from themselves. If they feel that an activity is too hard it means that they have to work on that to avoid unnecessary struggles while TAing
• The common theme across all activities is communication. Someone can be a good TA without much technical expertise, but no one can be a decent TA if he/she does not communicate clearly.

Students are expected to:

• Be on time
• Be ready having:
  • IDE / text editor open
  • Pen & paper
• Be participative

• Clone this repo.
• Create a tmp directory to copy & paste exercise templates.

• 4 weekly meetings
• 1 hour each
• Participants: 2 - 6
• Each meeting will have 2 main blocks
  • Homework presentation & feedback. In the first meeting this block is replaced by Introduction
  • Day activity execution

• Introduction
  • Go through the Onboarding presentation
  • How to use teachers' repo issues
  • How to use Slack
• Day activity: Dictate a method
• Homework Solve tickets from slack

• Solve tickets from slack devolution
• Day activity: Refactoring
• Homework Learn & tell

• Learn & tell devolution
• Day activity: Design a feature
• Homework Write an article

• Write an article devolution
• Day activity: Command line workout
• Homework Recommended reads

🏋️‍♀️

The facilitator will act as bootcamp student sharing his/her screen and presenting students with git, bash & config related issues. Students will take turns to solve these issues. If a student cannot solve the issue he/she has been assigned, the facilitator should ask all students to collaborate.

Further details & activity's material can be found here

📐

The facilitator will act as bootcamp student sharing his/her screen and presenting students with features to design. Students will take turns to elaborate on how they would tackle these features. The student's participation is considered completed when he/she provided the pseudocoding covering all the steps to develop the assigned feature. If a student cannot provide a proper answer, the facilitator should ask all students to collaborate.

Further details & activity's material can be found here

🗣

Students will take turns to dictate the provided method to peers. Peers can ask 1 (or should it be 2? 3?) question for clarification. At the end of the student's turn he/she will share his/her screen to display the dictated method. Peers will be able to see how far off their attempts were and feedback will be given to the student.

Further details & activity's material can be found here

👩‍🎓

Students are assigned a technical article. The following encounter they will have to share at least 3 things they learnt from it.

Further details & activity's material can be found here

📚

A list of articles for aspiring TAs & teachers to read.

Further details & activity's material can be found here

🧹

The facilitator will share his/her screen with code snippets to refactor. Students will take turns to refactor snippets. After his/her attempt a group discussion will start.

Further details & activity's material can be found here

🎟

Students have to help someone from any slack channel to solve a problem. In the upcoming encounter students will share their experience.

Further details & activity's material can be found here

✍️

Students should write a technical article. Ideally it should be something that could be applied during project weeks.

Further details & activity's material can be found here