Skip to content

Commit

Permalink
Update M2 repeater hub
Browse files Browse the repository at this point in the history
  • Loading branch information
kaylagordon committed Jan 11, 2024
1 parent 62920b6 commit 6920cbf
Showing 1 changed file with 10 additions and 11 deletions.
21 changes: 10 additions & 11 deletions lessons/module-2/mod-2-repeater-hub.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ title: Mod 2 Repeater Hub
Welcome! Please read this entire page completely. Reach out to your instructors if you have any questions!

## Repeating Guidelines
General information about repeating can be found [here](https://frontend.turing.edu/documents/repeat_guidelines_student_2020.pdf)
General information about repeating can be found in the Student Handbook [here](https://docs.google.com/document/d/1B84KoDHytY1yVLxRK9CTc1eipCx2XOS7PVkxYU0p2zA/edit#heading=h.lzq0jebf1oau)

## Slack Channels
Make sure you are part of the following channels:
Expand All @@ -15,17 +15,14 @@ Make sure you are part of the following channels:

## Gear Ups and Professional Development
**PD expectations for repeating Mod 2:**
You will be added to a new Homeroom group and are expected to attend Homeroom discussions and Mix It Up on Wednesdays. You are not required to attend the other PD sessions.
Repeating the module is a great opportunity not only to solidify your technical skills but also your professional development skills. [This plan](https://careerdev.turing.edu/module_two/m2_pd_repeat_plan) goes over some suggested ways to approach that. @allison_reu_singer is always available for support and coaching at the link in her Slack bio. You can reach out to her with any questions you have.
You are not required to attend the PD session, but you may choose to attend at any time.

**Gear Up expectations for repeating mod 2:**
You are expected to attend all Gear Up sessions, except for Week 1 which is optional for repeaters.
Repeating the module is a great opportunity not only to solidify your technical skills but also your professional development skills. We recommend that you continue to update your LinkedIn and resumes as you complete new projects. This is also a great opportunity to expand your network by setting up coffee chats and talking to Turing alums. Don't waste this extra time you have!

## Tips For Intermission To Prepare for Mod 2-Round 2

- It is not required that you re-do the Mod 2 prework. However, if there is something in the prework that you think would be valuable to review, go for it!
- As you commit to daily iterator practice, realize that the focus should be 90% problem solving and 10% iterators.
You need to be familiar with the iterator/mutator methods. However, the main skill you need to develop in Mod 2 is the ability to digest and break down complex problems into small steps/pieces so that you can solve them. This means you must nail down an effective problem solving process that you can apply to any problem placed in front of you.
- As you commit to daily iterator practice, realize that the focus should be 90% problem solving and 10% iterators. You need to be familiar with the iterator/mutator methods. However, the main skill you need to develop in Mod 2 is the ability to digest and break down complex problems into small steps/pieces so that you can solve them. This means you must nail down an effective problem solving process that you can apply to any problem placed in front of you.
- Review some of the difficult lessons and make a list of questions to ask during that lesson the following inning. Work through exercises in the lessons to help you better understand those concepts.
- Make a list of all the iterator and mutator methods, and go over each one’s use cases and syntax every night. Writing them out on paper or flashcards is more valuable than typing them out. They will stick in your brain better.
Pay attention to what each method returns. Pay attention to which are mutators.
Expand All @@ -39,11 +36,13 @@ You are expected to attend all Gear Up sessions, except for Week 1 which is opti

**Q:** *Should I complete jsFun over and over?*
**A:** No! You should only complete each test **once** this inning.
We recommend starting on [jsFunner](https://github.com/turingschool-examples/jsFunner) first. If you finish that, you can go back to a fresh copy of jsFun and begin anew.
We find that when students complete the same test suite more than 2 times, memorization and pattern matching kick in (which is not what we want!). These test suites should be improving your problem solving skills. If you feel yourself being able to write code without reading the full test, it's probably time for a new test suite.
We recommend starting on [jsFunner](https://github.com/turingschool-examples/jsFunner) first. If you finish that, you can go back to a fresh copy of jsFun and begin anew. We find that when students complete the same test suite more than 2 times, memorization and pattern matching kick in (which is not what we want!). These test suites should be improving your problem solving skills. If you feel yourself being able to write code without reading the full test, it's probably time for a new test suite. Here are a few more exercises, too:
- [Iterator Practice Gist](https://gist.github.com/kaylagordon/c1f62f2c43e27dee3c6176f4d54aa3b6)
- [Iterator Practice Repl 1](https://replit.com/@kaylaewood/iteratorpractice#index.js)
- [Iterator Practice Repl 2](https://replit.com/@kaylaewood/iteratorpractice2#index.js)

**Q:** *Should I reference my old projects when working on projects this inning?*
**A:** This is not a good idea. Remember, the projects are about learning, not completion. We'd rather you productively struggle through the logic on a project than just look back at how you did it last time and copy the answer. Also, this approach isn't fair to your project partner(s) who is seeing this stuff for the first time. We know it's tempting, but remember **it's about process over product**.
**A:** This is **not** a good idea. Remember, the projects are about learning, not completion. We'd rather you productively struggle through the logic on a project than just look back at how you did it last time and copy the answer. Also, this approach isn't fair to your project partner(s) who is seeing this stuff for the first time. We know it's tempting, but remember **it's about process over product**.

**Q:** *Should I get a head start on projects?*
**A:** You should not be working on projects before they are officially kicked off. There is plenty for you to work on if you finish a project early (hint: the **Extra Practice** section!). Projects are meant to be completed in the time allotted. Also, instructors make changes to project specs leading up to the kickoff. Finally, one goal of group/paired projects is collaborative learning and communication and that is sacrificed when students work ahead on these projects.
**A:** You should not be working on projects before they are officially kicked off. There is plenty for you to work on if you finish a project early. Projects are meant to be completed in the time allotted. Also, instructors make changes to project specs leading up to the kickoff. Finally, one goal of group/paired projects is collaborative learning and communication and that is sacrificed when students work ahead on these projects.

0 comments on commit 6920cbf

Please sign in to comment.