Project Week Overview
Last updated
Last updated
It's time for your first paired project week! For this project, you and a partner will build an application that interacts with a third-party API. You will fetch data, render the fetched data to the DOM, and then fetch some more data! In the end, you will have a deployed interactive application that connects with a web API.
The main technical goal of your app is to send two fetches and render the fetched data:
First, fetch a collection of resources (GET a set of users, a set of pictures, a set of authors) and render all of those resources
Fetch more details about a single one of those resources (GET details about a single user, a single picture, a single author, etc…) and then render those details
Check out called "Art Viewer". Notice that the application fetches a bunch of pieces of art but you can also click on a single piece of art to see more details. The search feature and the ability to choose how many pieces are shown per page are bonuses. Of course, you can do more than this, but this is the minimum idea!
While building your first portfolio-level project is certainly the main focus, there are a few other key learning objectives!
Demonstrate your skills learned from Mods 1-3: Core JavaScript, HTML & CSS, DOM Manipulation, and Asynchronous JavaScript
Develop teamwork skills including communication, problem-solving, compromise, and task management
Strengthen your Git workflow fundamentals, managing branches, navigating merge conflicts, and maintaining a repository
Practice Agile methodologies by managing a scrum board and by performing daily stand-up and stand-down.
Deploy a project!
Practice your technical communication through a presentation.
One of the easiest ways to get off track is by worrying about creating a unique project:
Student projects are not meant to be unique.
You're not creating a new app that addresses a gap in the market.
You aren't deploying this app for the purpose of having real users.
Student projects are meant for learning and demonstrating your learning
You may have a great idea that you really want to implement, but remember, you are working as a team and you only have a week. Time is not on your side and the more time you waste disagreeing with your partner about what features to implement or what API to use, the less time you'll have to actually build the thing.
Use branches and make PRs
Use your scrum board
Assign tasks
Don't do duplicate work
Be in alignment with your teammate outside of the scheduled meetings with your engineering manager
Actually write a fetch to make sure that the API works before choosing it for your proposal