Skip to content

Homework_Submission_Instructions.md

Latest commit

 

History

History
99 lines (80 loc) · 5.15 KB

Homework_Submission_Instructions.md

File metadata and controls

99 lines (80 loc) · 5.15 KB
Raw

Homework Submission

  • All homework is due at 12:01 PM (noon) the day before the next class.
  • All completed homework task links must be pasted into your HW Submission Sheet Google Sheet. (link to that is in bookmarked in slack).
  • Submit GitHub links to your PR completed exercise.

Homework Instructions: How to hand in your HWs.

HW assignments can be found in your syllabus under that week file

All HWs are due at 12:01 PM (noon) the day before the next class

  • Wednesday's class: HW due 12:01 PM on Tuesday
  • Thursday's class: HW due 12:01 PM on Wednesday
  • Friday's (both 12:30 PM and 06:30 PM): HW due 12:01 PM on Thursday

There are usually 3 sections of HW every week.

#1 Pre-Class HW [~1hr]

This covers the topic we are about to teach. This is HW that will help you come to class better prepared to learn the material that week.

  • Watch / read / do the tutorial listed above.
  • Go to your class slack channel.
  • Find the usually most recent message from your TA instructor that says "Week X: Pre-Class learnings".
  • Respond in-thread to that message with least one thing you learned from the videos/reading/or tutorial.
    • Your response can be It can be as short as one sentence, or as long as a book.
  • Still in Slack, copy the link to your response.
  • Pasted that to your response in HW Submission sheets Pre-Class column for that week.

Submit by pasting the link to your message under the "Pre-Class Slack Link" column.

#2 Exercise HW [~1hr]

This is a coding assignment that you usually start in class. It is located in the Exercise-DONT-EDIT-MAKE-COPY.ipynb file.

Instructions

A bot reviews every homework PR automatically. Two things decide whether it merges you: your filename identifies you and the week, and your PR contains nothing but your notebook. Steps 2, 4 and 5 are where essentially every rejection comes from.

  1. Make a copy of Exercise-DONT-EDIT-MAKE-COPY.ipynb.

    • Do not edit or submit the original template. Work only on your copy.

  2. Rename your copy. Aim for this shape:

    Firstname_Lastname_week_{NN}_exercise.ipynb

    Only two parts are actually enforced, so don't lose sleep over punctuation:

    • Who you are. Use Firstname_Lastname, or any identifier with a digit in it (e.g. a student number — but not your real CUNY ID, this repo is public). Initials alone are rejected — we share this repo across every section and initials collide for real. A single run-together word like janedoe is also rejected; separate your names.
    • Which week. A week number has to appear, and it has to match the week folder you put the file in.
    • Everything else is flexible: -, _ or a space as separators, any capitalization, and whatever you write after the week number (_exercise, _hw, _homework, or nothing) is ignored.
    • ✅ All accepted:
      • Faizan_Khan_week_03_exercise.ipynb
      • Faizan-Khan-Week-03-exercise.ipynb
      • faizan_khan_week3_hw.ipynb
      • student_12345678_week_03_exercise.ipynb
      • Faizan_Khan_Week01.ipynb
    • ❌ Rejected:
      • fk_week_03_exercise.ipynb — bare initials
      • faizankhan_week_03_exercise.ipynb — run-together name, no separator
      • Faizan_Khan_exercise.ipynb — no week number

  3. Complete all questions in your copy of the exercise notebook.

    • A copy that still matches the blank template gets flagged, not merged.

  4. Move it into the exercise/ folder for that week — e.g. Week-01-Pandas/exercise/.

    • Leaving it at the week's root (next to Lecture.ipynb) will be rejected.
    • The week number in your filename must match the week folder it's in.

  5. Your PR must contain your notebook and nothing else. This is the single most common reason a PR gets flagged.

    • Some exercises write a data file when you run them (Week 1 writes data/joined.csv). That file is not homework — don't commit it.
    • Don't commit the template, Lecture.ipynb, or anything under data/.
    • If you renamed or moved your file, delete the older copy — one notebook per PR.
    • Already committed something by accident? git rm --cached "path/to/file", then commit and push. The file stays on your computer, it just leaves the PR.

  6. One week per PR. Don't bundle Week 1 and Week 2 into the same pull request.

  7. Push your completed notebook to your fork.

    # NEVER DO:
git add .

# Instead, add only your exercise file:
git add YOUR-EXERCISE-FILE.ipynb
git commit -m "YOUR COMMIT MESSAGE"
git push

#3 LinkedIn Post [~10min]

Every week you have to post on LinkedIn. It can be anthing data science related unless instructed otherwise.

Publish the post (make sure its a public post.)

If no specific post topic is given that week, here are some topic ideas you can use.

  • It can be about starting your CTP journey.
  • Asking for advice on most important things to learn for entry level roles.
  • Something you leanred in the pre-class videos.
  • Why you love or hate pandas.
  • Your favorite part about the class.
  • A tip or trick that your learned in class.
  • Anything related to data science or your journey.

Submit by putting the link to your LI post under the "LinkedIn Post" column.