Fundamentals (Paid)
  • 🚀Course Overview
  • Course Logistics
    • 🏫Course Methodology
      • 🧩Course Components
      • 💬Community Channels
      • 🎲Course Projects
    • 💻Required Hardware and Software
      • ☝️Required Software 1
      • ✌️Required Software 2
      • 👍Recommended Setup
    • 🗓️Schedule
    • 💡Tips and Tricks
      • 📒Coding Strategies
      • 🛠️Tooling Pro Tips
    • 🎓Post-Course
      • 🎓LinkedIn Certificates
      • 🚂Bootcamp Admission Criteria
  • 1: Introduction
    • 1.1: What is Coding?
    • 1.2: Web Browsers
    • 1.3: Command Line
    • Additional Resources 1
  • 2: Basic Data Manipulation
    • 2: Operators and Expressions
      • 2.1: Arithmetic Operators | Mathematical Expressions
      • 2.2: Assignment Operators | Variables
    • 2.3: Our First Program
    • Additional Resources 2
  • 3: Structuring and Debugging Code
    • 3.1: Functions
    • 3.2: Errors
    • Additional Resources 3
  • 4: Conditional Logic
    • 4.1: Intro to Logic
    • 4.2: Pseudo-Code, Boolean Or
    • 4.3: Boolean AND, NOT
    • 4.4: Input Validation
    • Additional Resources 4
  • 5: Managing State and Input Validation
    • 5.1: Program Lifecycle and State
    • 5.2: Program State for Game Modes
    • Additional Resources 5
  • 6: Arrays and Iteration
    • 6.1: Arrays
    • 6.2: Loops
    • 6.3: Loops with Arrays
    • Additional Resources 6
  • 7: Version Control
    • 7.1: Git
    • Additional Resources 7
  • 8: GitHub
    • 8.1: Intro to GitHub
    • 8.2: GitHub Fork and Clone
    • 8.3: GitHub Pull Request
    • 8.4: GitHub Repo Browsing
    • 8.5: Deployment
    • Additional Resources 8
  • 9: JavaScript Objects
    • 9.1: JavaScript Objects
    • 9.2: Card Deck Generation with Loops
  • 10: Advanced
    • 10.1 HTML
    • 10.2: CSS
    • 10.3: The Document Object Model
    • 10.4: DOM Manipulation
    • 10.5: Advanced Debugging with Sources Tab
  • 11: POST COURSE EXERCISES
    • DOM
    • Further Readings
  • In-Class Exercises
    • Day 2: Basic File and Data Manipulation
    • Day 3: Functions
    • Day 4: If Statements, Boolean Or, Boolean And
    • Day 5: Program State
    • Day 6: Scissors Paper Stone Redux
    • Day 7: Loops
    • Day 8: Arrays and Loops
    • Day 9: Beat That Redux
    • Day 10: Moar Cards / Chat Bot
    • Day 11: Blackjack Redux, DOM
  • Projects
    • Project 1: Scissors Paper Stone
      • Project 1: Scissors Paper Stone (Part 1)
      • Project 1: Scissors Paper Stone (Part 2)
    • Project 2: Beat That!
    • Project 3: Blackjack
  • Past Projects
    • Drawing With Emojis
    • Guess the Word
Powered by GitBook
On this page
  • Project Presentations and Review
  • Code Review
  • Individual Review
  • Peer Review
  1. Course Logistics
  2. Course Methodology

Course Projects

Project Presentations and Review

Students present projects in class on the last day of each project. Presentations should cover the following.

  1. Demo

  2. Biggest challenges faced

  3. What they might do differently next time

In order to keep each presentation relatively brief, the presentation should be focused around the features of the game. The presentation is not a code review, as that would take up too much time.

Code Review

On days when projects are due, we will review each others' code in groups of 2 or 3 during class. If there is a group of 3, the triplet will do individual code review together so that everyone gets to review someone else's code, then split into 2 groups for pairing.

Individual Review

1) Clone Partner's Code

You'll be paired up so that you can exchange the links for your repos via your community channel. Remember that the forked repo is the one that is under your GitHub account, not Rocket Academy's. If you have forked the repo but haven't pushed your latest code to GitHub, take a moment now to git push. Let your partner know you're updating the repo. Run a git clone <REPO_URL> <NEW_FOLDER_NAME> to get a copy of your partner's code.

Note: You need to rename the folder when you clone if you already have a folder named after the repo where you're making the clone.

2) Run Partner's Code

Open the code in the browser and test it. What does it do? If you're not sure what it does look inside script.js to see.

3) Read Partner's Code

Read the code and answer the following questions.

  1. How does it work?

  2. Does it have any obvious errors?

  3. Does it implement something that you were trying to do?

  4. Does it implement a feature that you haven't started yet? How does the code work?

4) Play with Partner's Code

It may be helpful to make changes to the code to help you understand it better. Write some console.log that would help you figure out what the code does. Break the code in a certain way to prove how it works or doesn't work.

5) Discuss

Once both partners are done with #1-4, discuss what you saw.

Peer Review

You'll be pair programming on one person's project at a time. The goal is to get working versions for each person. The driver will be the person who is *not* working on their own code.

Once done with one person's code, send the code to your pair (it's their project) via a code snippet. Switch to work on the other person's code.

Note: If you are working on your partner's code you can't push to their repo because GitHub repos are read-only to non-owners by default.

If you both have working versions, implement a new feature in one of the projects together.

PreviousCommunity ChannelsNextRequired Hardware and Software

Last updated 8 months ago

🏫
🎲