Lesson Weekend

We'll start out this week by learning about some important programming concepts that will allow us to better work with data:

  • Arrays - lists of data or information
  • Looping - allows JavaScript to repeat an action until some condition is met

Then we'll dedicate the rest of the week to coding all day, putting into practice everything we've learned so far.

Each day's exercises will specifically explore the week's objectives. Remember that speed and quantity are not measurements of success at the end of a day...understanding is. While we expect you to review and share each other's work, there's a great saying that applies (with a slight Epicodus modification): "Don't compare your code to others, compare your code to the code you wrote yesterday".

This week also shifts where our attention will be focused. Over the past two weeks, we have been creating websites with HTML, CSS and Bootstrap. We've added effects with jQuery and gotten started on the basics of JavaScript. When a project was completed, we ran the code in the browser to display it.

In this section, we will continue to practice being really conscious of the separation of back-end business logic and front-end user interface logic. We'll focus on writing our own JavaScript functions that we will call from jQuery.

At the end of the week, you will be able to:

  • break problems down into behavior examples
  • build JavaScript functions that use arrays and looping
  • create HTML pages that use jQuery to call JavaScript functions

Independent Project Objectives

The code review will give you the opportunity to develop a project with the following objectives:

  • JavaScript business logic and user interface logic are separate.
  • Variable names are descriptive and use lower camel case (e.g. myVariableExample).
  • Code is clean, well-refactored, and easy-to-read. This includes correct indendation, spacing, and including only necessary comments and debugging tools.
  • Application implements a for loop and works as expected.
  • All previous objectives have been met.
  • Project is broken down into "plain English" specs, listed in README.
  • Project is in a presentable, portfolio-quality state.
  • You are able to discuss the flow of your code and the concepts behind it with an instructor using correct terminology.