- Complete all cultural learning objectives
- Complete all technical learning objectives
- Attend 2 guided pairing sessions with instructor (scheduled in the instructor's session availability calendar)
- "Hangout" the live-coding hangout each time you work on a challenge
- Have at least 6 pairing sessions with at least 3 different students, and give feedback using Feedbackinator each time.
- Rate 20 pieces of others' feedback in Feedbackinator (Meta-feedback)
- Communicate ideas clearly to pair and coach
- Provide kind, actionable, and specific feedback to pair
- Name your strategy for dealing with shame (compass of shame)
- Name a conflict that arose during a pairing session or interaction with a student or instructor
- Name some of your key strengths and weaknesses, both technical and in working with a team or pair
To be unlocked:
==========================
Reflection is vital to learning and growth. Objectives and challenges should not be thought of as items to check off; they are your opportunities to learn and grow as a programmer. Be mindful of each of the following questions after solving each challenge:
- Was your strategy for solving the challenge successful?
- What part of your strategy worked? What parts were challenging?
- What questions did you have while coding? Did you find answers to them?
- Are there any concepts that are still confusing to you?
- Bastard Book of Ruby: Object-Oriented Concepts
- Tutorials Point: Object Oriented Ruby
- Ruby Monk: Introduction to Objects
- Introduction to Refactoring
- Rubular: Play with Regex
- Tail Recursion vs. Tree Recursion
- Ruby for Newbies
- Ruby Variable Scope
- GangesLearning (Videos)
- The Well-Grounded Rubyist (Book)