Use this template to create your DTR with your job seeker accountability groups. Copy/past the template into a gist for your group to send to your Career Dev team adviser.
Group Members: Jeremy Poulter, Tim Nguyen, Charlie Bandstra, Justin Corbin, Elliot Mackinnon
Schedule for weekly meetings and regular Stand Ups (must have 2 meetings a week):
Project: Crate Project
Group Member Names: Ruby Rinken, Jeremy Poulter, Kevin McGrevey, Steven Meyers
Goals and Expectations for the Project (What does each group member hope to get out of this project? What do we want to achieve as a team? How will we know that we're successful?):
Learn to code in a different language
Get through the entire project, consider extensions only if we have surplus time. Better to have good code rather than a lot of lower quality code.
-What is a "framework?" And how does it differ from a "library?"
A framework relative to a library is usually more complex because all of the control flow is already provided for the developer. This is different than a library which is just a collection of various class definitions that are available for use to a developer but on an individual basis where the developer can pick and choose what to include. The collections in a library are essentially re-usable code that can save a developer a lot of time and effort from having to recreate these definitions from scratch. An example of a library that we have been using is the chai assertion/expectation library where we use the definitions to instruct the code to look for certain things in our tests. We use this alongside our framework which in this case would be mocha. A framework like mocha provides the developer with the entire structure/features necessary to be able to make and run tests.
-Why should we consider using a framework over vanilla JS like y
Goals and Expectations for the Project (What does each group member hope to get out of this project? What do we want to achieve as a team? How will we know that we're successful? YES, you can still fully answer this question without knowing exactly what you're going to build.):
Out of this project we both hope to get a good practice and a full understanding of how to actually use and implement array prototype methods in real example use cases. Our achievement goals is to have a really well done project that covers all of the iterations and is something that we can be proud of. That means having full functionality, and a very polished look to the finished product.
| # DTR: Define the Relationship | |
| One teammate should copy and paste the *raw* markdown into a gist of your own. | |
| ### Guiding Questions to Define The Relationship: | |
| * What is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches? | |
| Leah prefers pair programming, using the driver-navigator method. Jeremy and Kyle prefers the pair programming in combination with divide and conquer approach once everyone feels comfortable with the topic/material. |
As the name implies, this tidbit emphasizes the importance of not using the word "AND" in a function name because this typically implies that you are assigning multiple duties to a single function. The root of this problem is that each function should only be assigned with one responsibility which the author calls the "Single Responsbility Principle". Functions are assigned with a single responsibility because it keeps the JavaScript code organized, easier to understand, and more capable of being changed. In coding, changes are made all the time whether it be because of newly learned information or finding a better approach to doing something, old code will be revisited and edited accordingly. Making changes to this code becomes increasingly difficult when multiple tasks fall under one function, because editing any one of those tasks can result in changes or even breaking of the other tasks. Often times, chang
