fse_selfpaced_curriculum - GitLite

KO | EN

gitlite — search

#javascript #python #llm #golang #go #deep-learning #docker #macos #awesome #cli #awesome-list #vue #ios #open-source

fse_selfpaced_curriculum

(★ 69)

No description available.

파일 탐색기

최종 버전 다운로드 (.zip)

- ajax.md
- Basic HTML Tags.png
- Big_0_Notation.pdf
- bob_class.png
- bobs_lic.png
- boxing.png
- bst.png
- class_def.png
- code_platoon.png
- Code_Platoon_Debugging_Guide-page-001.jpg
- Code_Platoon_Debugging_Guide.pdf
- concerts_and_news_app.gif
- cp_fullstack_development.png
- create_new.png
- devtools.png
- directory-structure.jpg
- django-architecture.png
- Django_Intro.pdf
- django_request_response_cycle.png
- DOM.svg
- DOM_example.png
- environments.png
- files.png
- for.png
- func.png
- get.png
- hash_visualization.png
- hipcamp.png
- hr.md
- html_static_page.png
- inspect.png
- installfest-docker.md
- installfest.md
- installfest_ubuntu.md
- Intro_Django_ORM.pdf
- javascript_control_flow.pdf
- JSFundamentalsDay1.pdf
- keyboard-setup.png
- lamassu.png
- letter.png
- lic_class.png
- license.png
- macinstallfest.md
- name-repo.png
- new_repo.png
- persistence-intro.md
- post.png
- post_response.png
- postman.png
- putsreq.png
- python-oop.md
- python_fundamentals.md
- React_Intro.pdf
- recursion.pdf
- rest.md
- sacramento_re_transactions.csv
- sally_class.png
- sallys_lic.png
- sql-queries.md
- The_Command_Line.pdf
- Ticketmaster_Challenge.pdf
- ticketmaster_req_res.png
- twist.png
- two_branches.png
- url.png
- well_crafted.png
- wine-instance.jpg
- wine-list.jpg
- day1-loops_objects.md
- day2-functions.md
- day3-classes.md
- day4-classes-2.md
- README.md
- README.md
- w1-d1.md
- w1-d2.md
- w1-d3.md
- w1-d4.md
- w1-d5.md
- README.md
- w2-d1.md
- w2-d2.md
- w2-d3.md
- w2-d4.md
- w2-d5.md
- README.md
- w3-d1.md
- w3-d2.md
- w3-d3.md
- w3-d4.md
- w3-d5.md
- README.md
- w4-d1.md
- w4-d2.md
- w4-d3.md
- w4-d4.md
- w4-d5.md
- README.md
- w5-d1.md
- w5-d2.md
- w5-d3.md
- w5-d4.md
- w5-d5.md
- README.md
- w6-d1.md
- w6-d2.md
- w6-d3.md
- w6-d4.md
- w6-d5.md
- README.md
- w7-d1.md
- w7-d2.md
- w7-d3.md
- w7-d4.md
- w7-d5.md
- README.md
- w8-d1.md
- w8-d2.md
- w8-d3.md
- w8-d4.md
- w8-d5.md
- README.md
- w9-d1.md
- w9-d2.md
- w9-d3.md
- w9-d4.md
- w9-d5.md
- README.md
- w10-d1.md
- w10-d2.md
- w10-d3.md
- w10-d4.md
- w10-d5.md
.gitignore
assignments.md
README.md

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# 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](https://docs.google.com/spreadsheets/d/1tD2ko3ykKCoe6S4vMSt49W_aZPtl3x05jWRMk2OWTsQ/edit?usp=sharing), which is broken down by weeks and days.

![Fullstack Development](https://github.com/codeplatoon/curriculum/blob/master/page-resources/cp_fullstack_development.png)

Click [here](https://docs.google.com/document/d/1KgNFbDhihSJv6OGYjFDhESaDJ6ljOyVoRQse7oQH1I0/edit?usp=sharing) to view the student handbook.

## Asking Questions in Slack / Slack Etiquette
Please join the Code Platoon's `#self_paced_curriculum` Slack Channel [here](https://join.slack.com/t/codeplatoonteam/shared_invite/zt-tu65s5qq-Cn~6K0vnDE0S4tBaY3OhsQ).

Before anything, read through [Slack etiquette](https://slack.com/blog/collaboration/etiquette-tips-in-slack).

Questions should be asked in the `#self_paced_curriculum` public Slack channel using proper [formating](https://slack.com/help/articles/202288908-Format-your-messages) (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](https://www.codewars.com/)
4. Visit [Pramp](https://www.pramp.com/promo/codeplatoon) to interview with other people - we have an agreement with them to get their premium plan for free!
5. [Interview Cake](https://www.interviewcake.com/)

## Video Links
Classroom videos/lectures will be recorded and posted to [YouTube](https://www.youtube.com/channel/UCASZ7zW_Egu0T4KG3YEdGfw/videos). 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](https://docs.google.com/spreadsheets/d/1nX1ylt8AOWVnwZ5v-naN7K2bfhlfZm8TRzepOuXdqWw/edit#gid=0) and add your own for future cohorts!