Goals: Create an application that consumes an API.

Warm Up

---

Work through this list of common interview questions with your partner at the start of the next two class sessions. Once again, this may be formatted as a mock interview, or you may discuss potential answers together:

Non-Technical

• What about coding interests you? What are your favorite parts?
• What's your workflow like when you sit down to create an application?
• What made you decide to attend a coding bootcamp?

General Coding

• What are the advantages to testing your code. What about disadvantages?
• How do you integrate testing into your general workflow when creating an application?
• Describe an HTTP GET request.

Code Snippets

• What value is returned from the following statement:

"i'm a lasagna hog".split("").reverse().join("");

• Write a brief function (in the language of your choosing) to check if two strings are anagrams.
• How would you count occurrences of a character in a string?

Code

---

API-Consuming Application

For this classwork, you and your pair will build an application that interacts with an API that you (or your classmates) built during the first half of the section. If you're using a classmate's API, make sure you clone or fork the project and push changes to your own repo. Your goal is twofold: continue improving the API itself and make an application for users to interact with!

You can choose to continue working with your pair that you built your API with, or you can choose to work with another pair.

On short weeks, you'll have less time to build an API-consuming application. Remember that you'll be expected to implement at least one of the seven objectives from the Further Exploration lesson for this course section's independent project, so if you don't feel comfortable with any of these objectives yet, take the time to practice further.

Peer Code Review

---

• Application successfully returns responses for each API call.
• Application handles exceptions.
• Application includes custom routes and model scopes.
• All routes are tested with request specs.
• README thoroughly describes all endpoints along with parameters that can be used.
• Application works as expected.
• Project is in a presentable, portfolio-quality state.
• Project demonstrates understanding of all concepts covered in this course section. If prompted, you can discuss your application using the correct terminology.