HOMEWORK

Below you will find homework assignments; these are assigned on Wednesday and due the following Monday. This page will be updated weekly.

WEEK 01

Homework: Due Monday 2/12

  1. Complete units 1 and 2 from Codecademy's Learn the Command Line (ignore paid content) (30-60 minutes)
  2. Codecademy Functions (30-60 minutes)
  3. Reading:

Optional

The Command Line Crash Course (2-3 hours)

WEEK 02

Homework: Due Wednesday 2/21

  1. 99 Bottles of Beer (30-90 minutes)

    starter-code > Homework-1 > 99-bottles-of-beer

  2. Fizzbuzz (60 min)

    starter-code > Homework-1 > fizzbuzz

    1. Construct a for loop that iterates through and console.logs the numbers 1 - 100.
    2. Add an if/else statement that logs the string "fizz" if the value being iterated over is divisible by 3; otherwise, log the value.
    3. Add an else if clause that logs the string "buzz" if the value being iterated over is divisible by 5.
    4. Add an additional else if clause that logs the string "fizzbuzz" if the value being iterated over is divisible by both 3 and 5.
  3. Temperature converter (60-90 min)

    starter-code > Homework-1 > temp-converter

    1. Create a function that accepts a temperature value in Fahrenheit and converts it to Celsius.
    2. Create a second function that accepts a temperature value in Celsius and converts it to Fahrenheit.
  4. Reading

Optional

  • Random address generator (30-60 min)

    starter-code > Homework-1 > BONUS-random-address-generator

  • Madlibs

    starter-code > Homework-1 > BONUS-madlibs

    We haven't covered all of the concepts necessary to complete this project, but we will pick them up over the next few weeks. Identify syntax in the code that you recognize, and research any code you encounter that you don't understand. This project will be due in a few weeks, so if you're looking for a preview of upcoming content, this will give you a head start.

WEEK 03

Homework: Due Monday 2/26

  1. Outline and create objects (30-60 min)

    starter-code > Homework-2 > object-homework folder

  2. Read about Hubot (45 min)
  3. Interact with the bots in our class Slack organization (only works in DMs with these bots, or in channels that they are members of, such as #general) (30 min)
    • @slackbot
      • Direct message with a question
    • @plusplus
      • Add ++ after the @ name of a user to give them a point
      • Direct message help to @plusplus to learn other commands to experiment with
    • giphy
      • Type /giphy and a space, followed by a word
      • giphy responds with an animated GIF related to that word
  4. Read the Project 1 description and start thinking about what you'd like your bot to do. (We will configure our computers and start building bots in class next week, so no need to start coding yet.) (30 min)
WEEK 04

Homework: Due Monday 3/5

  1. Slack bot
    • Finish your Slack bot
    • Create a new GitHub repo for your bot, including:
      • the JS code for your bot
      • updates to the default README.md file that documents what your bot is capable of and how to interact with it
    • Push your code to your repo, then use Slack to send Sasha & Aurielle a link to the repo
  2. Outline and create objects (30-60 min)

    starter-code > Homework-3 > object-homework folder

  3. Convert between JavaScript objects and JSON (30-60 min)

    starter-code > Homework-3 > json-homework folder

  4. Reading

Optional

    Visual Studio Code settings

    The Visual Studio Code editor relies on a user-editable JSON file for custom settings. Open and view this file by pressing command+, (Mac) or Ctrl+, (Windows/Linux). The document that opens shows the default settings on the left, and allows you to add custom settings on the right to override the defaults. Read through the default settings and their descriptions on the left, and then customize at least two settings with your own values on the right side. Save your changes, restart the editor, and verify that the changes you made are reflected in the editor.

    Visual Studio Code settings documentation

WEEK 05

Homework: Due Monday 3/12

  1. Madlibs (30-60 min)

    Homework-4 >madlib-with-loops

  2. 99 Bottles of Beer in the browser window (30-60 min)
    • Remember the 99 Bottles of Beer assignment? For this assignment, you'll be creating a website that programatically displays the lyrics to that song in the browser window.
    • You'll need to create both an HTML file and a JavaScript file.
    • In your HTML file, you'll want to have an unordered list (<ul>) that contains all of your lyrics.
    • Each line of the song should appear inside of a list item (<li>) within that unordered list.
    • Your JavaScript file should programatically append each line of the song to the page--no hard-coding lyrics in HTML!
    • Code this project using vanilla JavaScript methods.
    • Then refactor your code to use jQuery instead (preserving your original code in comments)
  3. Reading (60-90 min)

Optional

  • Dice (30-60 min)

    Homework-4 >BONUS-dice

    • Create an app where every time the user hits the "Roll Dice" button, the screen randomly updates each of the two images to display an image of a die corresponding to the value rolled.
    • Specific instructions in the js > app.js folder
WEEK 06

Homework: Due Monday 3/19

  1. Customizable survey form (90 min-2 hours)

    Homework-5 > jquery-homework

  2. Pre-work for Project 2: Feedr (2 hours)

    (Final project due Monday 4/2)

    • Read project overview
    • Research and choose APIs to use
    • Read API documentation for the APIs you've selected
  3. Reading
WEEK 07

Homework: Due Monday 3/26

  1. Current weather (60-90 min)

    10-ajax-apis > starter-code > 4-jquery-ajax-exercise

    Be sure to remove your API keys and app keys from your code before pushing to GitHub

  2. Project 2 (Feedr)

    Pseudocode the basic API functionality & DOM manipulation code

  3. Final project
    • Read the project overview.
    • Come up with a basic idea for your final project. Create an outline/project description that details how your project will meet each of the project requirements.
    • Create a list of possible APIs to use.
  4. Reading

NOTE: The Project 2 and Final Project tasks are milestones that are meant to help you make incremental progress on these large projects, but do not include work that you must submit with your homework. I strongly encourage you to complete these tasks by the deadline to avoid getting overwhelmed by work as the end of the course approaches. I am also happy to review and discuss your work on your projects at any point.

WEEK 08

Homework: Due Monday 4/2

  1. Project 2 (Feedr)

    Completed project due

    • Send Sasha & Aurielle the URL for your fork of the Feedr repo on GitHub
    • Remember to remove your API keys from your code before pushing to GitHub
  2. Final project milestone

    Pseudocode of basic features & draft of HTML/CSS code

  3. Reading

Optional

WEEK 09

Homework: Due Monday 4/9

  1. Final project milestone

    Final HTML/CSS code, draft of basic API functionality and DOM manipulation code

WEEK 10

Homework: Due Wednesday 4/18

  • Completed final project & presentation!

Optional