Group Member Names: Jonathan, Jeremy, Kyle, & Tanisha

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.):

Jonathan: Solidify redux and striving to test sad paths regarding testing. Kyle: Solidify redux and also focusing on how to handle sad paths regarding rendering and creating sad path tests.

• What is a "framework?" And how does it differ from a "library?"

A framework and a library are both dependent on rules. However, a framework has stricter rules than a library does. A framework can be thought of as the shell that executes code or "calls to the code" and is much more difficult to modify/customize. A library, on the other hand, is a collection of smaller pieces of code that can be used just about anywhere in the codebase.

• Why should we consider using a framework over vanilla JS like you have been doing in mods 1 and 2?

We should consider using a framework because it makes it easier to update the UI (the DOM) based on the state of the data. With a framework, we can define our UI at the beginning, without worrying about updating each time an action changes the data related to that UI, as the framework will automatically do it for us. A framework helps us to write code that's more complex in an efficient manner.

Group Member Names: Jordan A Whitten & Tanisha L Davey

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.):

To finish the project and make it look nice. Become better at using classes and testing of those classes. We'll know we're successful when we get through all the iterations.

• Munchie Madness v.2

One teammate should copy and paste the raw markdown into a gist of your own.

• What is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches?
• How do you communicate best? How do you appreciate receiving communication from others?
• How would you describe your work style?
• What are each of our strengths? How can our strengths complement each other?

• What does the engineering department looks like? Frontend team? Backend team? Everyone fullstack? How many individuals make up the team?
• What percentage of your day is spent working on code (writing code, pairing, doing code-reviews, etc.)? Outside of coding, what does the rest of your day look like?
• What technologies/programs does your company currently work with?
• How is work assigned?
• Do you/the development team have a say in the decision making process (re: product, workflow, etc.)?
• What's most exciting for you in your current role? Company?

• What is the DOM? by Ire Aderinokun
• What, exactly, is the DOM? by Kara Luton
• What exactly is the DOM?! by Chris Coyier

What did I learn?

The DOM is not the HTML, not what you see in your DEV tools, and it is not what a user sees in their browser. Essentially, it is not something you can actually see. DOM is an acronym for Document Object Model. It's the HTML source turned into an objct that models/shows a representation of the HTML. The DOM is what allows programs, like JavScript to manipulate the HTML rendered (what a user sees on the page).

• add a link to the specific tidbit
• write up a short paragraph on each detailing what you learned and how you hope to use your new knowledge in the future!

In this tidbit, Samantha teaches the reader how to change the cursor color using the CSS property caret-color. Caret is another name for the cursor when it becomes the blinking line inside a text box signaling that a user can type into the text box. This property can be used on html elements where a user can input text including: <input>, <textarea>, and elements that allow the contenteditable attribute to be used. I can see myself using the caret-color propertu if I wanted to design and code a page to have a specific theme, having all elements within that page adhere to that theme, instead of relying on the default caret color (black).

• Login Form Comp
• Greeting App Comp
• Friends Comp

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.):

Our goals for this project is to have a clear understanding of how to implement classes and objects as a dynamic tool. Other things we'd also like to keep practicing include using event objects/targets, as well as the use of grids and flexboxes in our CSS. We will also be including the agile processes that we learned about: working in agile and being agile through the use of daily stand-ups (at lunch) and group retros (3 times during the duration of the project).

Team strengths & collaboration styles (consider discussing your Pairin qualities here):