Editing Adie Tutor

Jump to navigation Jump to search

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.

Latest revision Your text
Line 1: Line 1:
'''Tutors'''<br />
'''Tutors'''<br />
Ada tutors meet individually with students who could use some extra support, either by their own assessment or by their instructors’. We strive to make tutoring available to any student who requests it, and our tutors are often a key support to student success in the program. The tutoring program creates space to work through problems with individualized support and the opportunity to ask more questions than there’s time for in class.  
This opportunity is for previous Adies to share their technical experience and knowledge with current Adies.
Tutors commit 1.5 - 2 hours a week, and schedule independently with their assigned student. Many pairs meet at Ada, but some choose to meet in a different location, especially if they live in the same neighborhood. Tutors usually commit to being available for the duration of the cohort, which may be 1-6 months depending on when they sign on. However, shorter term tutoring opportunities are also available.  
  '''To be an Adie Tutor''', please email program@adadevelopersacademy.org so we can add you to the Ada Tutors mailing list.
As a '''Student/Alum Tutor''', you will provide 1-on-1 support to current ADA students.
  '''To become a tutor''', please complete this brief [https://forms.gle/MCB5P7idSiCimqhc7 volunteer application] or email volunteer@adadev.org with any questions.
'''Your role will be to:'''
* Help students with technical questions and concepts on either an on-going or one-off basis
* Tutors are essentially personal [[Teaching_Assistant|Teaching Assistants]]
'''Your role as a tutor will be to:'''
*Provide expertise knowledge to students on why/when/how coding structures are used
*Help students get "unstuck" by asking them probing questions, providing suggestions, and scaffolding the process of solving a problem
*Provide specific feedback to students about their code and problem solving approach
*Encourage and support students on their journey to being professional developers
*Provide supportive code review that helps them level up their work without feeling judged or condescended to.
''Tips on Being a Great Tutor''
Cultivate independence:
*Demonstrate HOW to do something, and then ask the student to re-teach you.
*Make sure the student is the one actually doing the work (i.e. Don't just take over! Let the student “drive” the keyboard.)
*Offer additional examples/questions to “quiz” the student
*Aim for improvement and long-term growth—not perfection!
*Help them do the best work THEY can do (not the best YOU can do)
*Be a good listener
*Listen to what the student is asking for help with. Make sure you know the student’s current learning goals and current questions.
*Ask for explanations of answers—particularly incorrect ones. Try to lead students to identifying their own misconceptions when possible.
If you hear the same question numerous times, you may have identified an area where the student lacks some core conceptual understanding.
Be available to answer students’ questions about the industry as a whole, interviewing, and job searching.
♦♦Please inform Ada staff should you have concerns about a student emotionally or academically.♦♦
*Offer praise and encouragement, but without being phony
*Acknowledge progress, even if there are still struggles/errors
*Never ridicule incorrect answers
*Share your own struggles and strategies
*Provide constructive feedback
*Demonstrate Positive Intention: Give comments with care and kindness.
*Describe, Don’t Evaluate: Feedback should describe, rather than judge, a student’s work. For example, “You’ve broken this problem down into really good functions that eliminate redundancy of code and allows for specific code functionality testing” rather than “This code looks good” (which is a judgment and doesn’t describe what makes the code “good”.)
*Be Specific, Not General: Give specific comments rather than general ones. For example, “In this section of code we could eliminate some of the loops if we…” rather than “This algorithm could be more efficient.”
Balance Feedback, Use the “sandwich” approach:
    1. Say something that worked well,
    2. Offer a constructive suggestion for improvement, and
    3. Mention another aspect that worked well.
    For example, “I really like the UI for your form, but perhaps the controller could store the data using a…. Overall, the breakdown
    of the problem is good, though!”
    This approach will build a student’s confidence levels while they are developing their skills.
*Check Understanding: Check that the student understood your feedback. Ask the student to paraphrase what you’ve explained. Sometimes if the student verbalizes it, it can either affirm understanding or lead to additional questions.

Please note that all contributions to Ada Developers Academy Wiki are considered to be released under the Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) (see Ada Developers Academy Wiki:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

Cancel Editing help (opens in new window)