We’re done with both requirements documents. It’s time to push the branch to GitHub. In this episode, you’ll: Push the branch to GitHub Create a Pull Request (PR) Change the master repo to your GitHub account instead of the original on Know the Code Walk through the PR GUI Merge it into the master branch Delete the requirements branch Pull the updated master branch down to your machine to sync you up with GitHub
Labs
Labs are hands-on coding projects that you build along with Tonya as she explains the code, concepts, and thought processes behind it. You can use the labs to further your code knowledge or to use right in your projects. Each lab ties into the Docx to ensure you have the information you need.
Each lab is designed to further your understanding and mastery of code. You learn more about how to think about its construction, quality, maintainability, programmatic and logical thought, and problem-solving. While you may be building a specific thing, Tonya presents the why of it to make it adaptable far beyond that specific implementation, thereby giving you the means to make it your own, in any context.
Testing Strategy
Continue Building Tests Scaffolding
Build Tests Scaffolding
Build Test for Get Item
Build the Get Item Scaffolding
Push to GitHub, PR, Merge, & Sync
Document the API Basics
Let’s create a new requirements document for the Data Store’s API. Then we work together to layout how we are going to build it.
Review
In this episode, we’ll review what we’ve done so far and then discuss what we’ll do next in this lab as part of our planning.
Planning Introduction
You’ll be introduced to the lab and what you’ll be doing in it. You’ll learn that the best practice in development and engineering is to first planning out what you are going to build before you start coding.
