Skip to content

Latest commit

 

History

History
45 lines (33 loc) · 3.55 KB

README.md

File metadata and controls

45 lines (33 loc) · 3.55 KB
Raw

Code Platoon Curriculum

Welcome

Students, welcome to Code Platoon! Be prepared to push yourself and to work hard towards your new career. We are happy you are here and are here to support you. If you need anything, please don't hesitate to ask. There are many resources available to you on your journey!

Getting Started

You can view our cohort's curriculum calendar, which is broken down by weeks and days.

Fullstack Development

Click here to view the student handbook.

Asking Questions in Slack / Slack Etiquette

Please join the Code Platoon's #self_paced_curriculum Slack Channel here.

Before anything, read through Slack etiquette.

Questions should be asked in the #self_paced_curriculum public Slack channel using proper formating (see Inline code section), not via TA or instructor DM. This reflects the industry norms - companies want their engineers to have discussions publicly so that questions can be easily searched and referenced.

Your questions should be pointed (i.e., not "Can someone help me?"), show that you’ve read through the code/error, should contain your thought process / some potential solutions, and should not be anything that is easily Google-able. Once you ask a question and find a solution, please update your question thread so that other students can benefit from seeing the question and answer.

Submitting Work for Review

  1. Navigate to your desktop from your terminal(cd ~/desktop)
  2. Hit the Fork icon on the top right to copy the repo to your username instead of codeplatoon
  3. Clone down the repository to your desktop (git clone REPO_LINK.git)
  4. Checkout a new branch (git checkout -b SOLO/PAIR_YOUR_GITHUB_USERNAME)
  5. Update whatever work you need to
  6. Add the changes (git add CHANGED_FILENAME)
  7. Commit the changes (git commit -m "SOME MESSAGE HERE")
    • Repeat the above three steps until you've completed your work, and it's ready to review
  8. Push the changes up to Github (git push origin NAME_OF_BRANCH)
  9. Open a pull request, comparing your forked branch to the original master branch

What should I do if I finish everything on any given day?

  1. Help those around you. Teaching solidifies learning.
  2. Watch tomorrow's video to get yourself a leg up on the next day!
  3. Go through Code Wars
  4. Visit Pramp to interview with other people - we have an agreement with them to get their premium plan for free!
  5. Interview Cake

Video Links

Classroom videos/lectures will be recorded and posted to YouTube. If you need lecture videos immediately, please bring a USB drive to Tom, Ankur, or Chad and we'll get you the video.

Student Resources

Students from previous cohorts have added a list of resources that they found helpful broken down by week and day. Please take a look at this link and add your own for future cohorts!