This repository is yours to keep track of what you've covered so far, to get to know each other, to share helpful resources, to practice collaboration workflows, ... to do everything!
Slack is great for chatting but links and good explanations can easily get lost in message history. Think of this repository as your class' forum and home page.
- Modules
- Workflows
- Typical Week
- Students
- Coaches
- Study Stuff
-
3 weeks | check-ins | projects | roll-calls | milestone
-
2 weeks | check-ins | projects | roll-calls | milestone
-
2 weeks | check-ins | vocabulary | roll-calls | milestone
-
4 weeks | check-ins | javascript | roll-calls | milestone
-
3 weeks | check-ins | snippets | roll-calls | milestone
-
3 weeks | check-ins | projects | roll-calls | milestone
-
2 weeks | check-ins | projects | roll-calls | milestone
-
2 weeks | check-ins | projects | roll-calls | milestone
-
3 weeks | check-ins | projects | roll-calls | milestone
-
5 weeks | check-ins | projects | roll-calls | milestone
-
2 weeks | check-ins | projects | roll-calls | milestone
-
6 weeks | check-ins | projects | roll-calls | milestone
A short guide to using the issues in this repo.
You can attach this label to any issue or PR that you need help completing. If the code you are blocked on is in another repository, you can create a new issue using the help-wanted template to describe your problem and link to your code.
Got a question about anything? Go ahead and ask! You can use this label on an existing issue/PR, or create a new issue to discuss your question.
Each module you will create a new check-in issue. You will use this issue to keep track of your self-study progress, and to post a check-in each Wednesday including:
- Progress: What went well so far this week?
- Blocked: What blocked you this week? How did you get past it?
- Next Steps: What will you work on for the rest of the week?
- Tip(s) of the Week: Did you find a neat trick or a helpful link this week?
For each project (individual or group) you will place a new issue on the Class Projects board.
- If you are blocked, add the
help-wantedlabel - When you think you're finished, move your issue into the Ready for Review column
- If your project is complete, a coach will move it into the Done column
- Else they will move it to Needs Revision. When you've addressed the feedback you can move it back into Ready for Review
Each Sunday before class your coach will create a new Roll Call issue. Leave a little comment to say hello and let us all know how your week went.
Throughout the HYF course and your overall career as a programmer, you will control your own fate. 35 hours of study is just the bare minimum to get by at HYF, not enough to fully prepare you for your first job.
The more you know and the harder you work, the faster you will find yourself in a career you love.
The more you participate and become part of the HYF community, the more people are going to be willing to help you in return.
- 10:30 - 11:30: Career Skills
- Guest workshops covering important skills that are not in the core curriculum
- These will not happen every Sunday
- 11:30 - 12h: Prep
- leave your comment in the week's
roll-call - go over any
questionissues together
- leave your comment in the week's
- 12h - 16h: Class
- Review
- Presentation 1
- Group work
- Break
- Presentation 2
- Group work
- Homework Launch
- Plan the week's project
- Set up the project repository
- Individual study
- Begin developing the project
- Individual study
- check-in!
- Class review call (if you organize one)
- Individual study
- Begin prep work for Sunday
- Individual study
- Weekly project MVP
- Merge all
must-havePRs - Stop adding new features
- Make sure what's there works
- Move your issue to READY FOR REVieW
- Merge all
- Individual study
- Family, friends, rest & play
- Individual study (optional ;)
