cbdallavalle

Code reviews are a very common practice in the workplace and you start doing a lot of code reviews in the workforce. We want to give you a bit of practice in looking through and review code that you haven't seen before. 

In the groups below, you have been paired with someone from another rancid tomatillos group. We would like you to start a slack message with your partner and the instructors. 

Share with each other:
- which solo iteration you did
- the last branch you worked on for your solo iteration (this can be your default branch)

As you all do your code review, work through the Rancid Tomatillos Rubric, here: https://frontend.turing.io/projects/module-3/rancid-tomatillos-v2.html. Your feedback for your partner should include the number they meet on the rubric,  with additional feedback on areas they did well and areas they can grow in.

cbdallavalle

Now that you've spent some time playing around with Express, we would like you to BYOB (build your own backend)! You will be responsible for creating data in your backend and building a server so you can get and post data. This project shouldn't take more than 3 hours to complete.

Base Expectations:

1. Create a Data Source

Pick some data you are interested in. It could be anything - birds! podcasts! games! Then build out what your data set will look like in your app. You data set should be an array of objects that represent an item from the set of data you chose. As you are building out, ask yourself - what properties will you need to create for each item? What data needs to be stored on those properties?

You only need to have a minimum of three pre-made objects included in your server.js file.

cbdallavalle

Comment below with your names and link to your project repo:

cbdallavalle

Promises
1.testnum
testnum = (num) => {
  if(num > 10) {
  resolve(`${num} is greater than 10, success!`)
  } else {
  reject(Error(`${num} is less than 10, error!`)
  }
}

cbdallavalle

Project:

Group Member Names:
Casey & Alex

Project Expectations: What does each group member hope to get out of this project?
A: Get the code as dry as possible and a deep understanding of react
C: Concise and practical tests, nail it out of the park

Goals and expectations:

cbdallavalle

Project:

Group Member Names:
Valentino & Casey

Project Expectations: What does each group member hope to get out of this project?
V: Better understanding of the tools we are using and when to use them, especially retreiving data that is nested 
V: Know and understand every step we are doing, and valuing what we create instead of finishing the project
C: I'd like to finish project, but have content that we understand

cbdallavalle

Project: Linked List
Group Member Names: Edgar and Casey
Project Expectations: What does each group member hope to get out of this project?
	-Edgar: solidify jQuery, learn responsiveness
	-Casey: be introduced to jQuery, work on CSS, learn responsiveness
Goals and expectations:
	-Finish phase 3
	-Split the work in half
	-Over weekend finish phase 1
Team strengths:

cbdallavalle

1. Learner, input, activator, restorator. I have been using my learning and restorator strengths consistently during mod1. I am an avid learner and often thrive in environments like Turing where I learn something new every day. Even though the lessons and projects can be overwhelming at times, my love to solve problems and the energy I receive from challenges keeps me going. When I first took the strengths finder, I was not sure how much input was a part of my persionality. I did not identify with being a collector, in fact, all throughout my childhood the only thing I collected were dirty clothes on my bedroom floor. As I spent more time at Turing, I realized that I do collect information, though. I often log away in my brain different facts from lecture and my own independent study to use later in my code. I also store tidbits of information about other people and use them later in our interactions. I have seen aspects of my strengths play out while at Turing, and I now recgonize those strengths and capitil

cbdallavalle

1. Learner, input, activator, restorator. I have been using my learning and restorator strengths consistently during mod1. I am an avid learner and often thrive in environments like Turing where I learn something new every day. Even though the lessons and projects can be overwhelming at times, my love to solve problems and the energy I receive from challenges keeps me going. When I first took the strengths finder, I was not sure how much input was a part of my persionality. I did not identify with being a collector, in fact, all throughout my childhood the only thing I collected were dirty clothes on my bedroom floor. As I spent more time at Turing, I realized that I do collect information, though. I often log away in my brain different facts from lecture and my own independent study to use later in my code. I also store tidbits of information about other people and use them later in our interactions. I have seen aspects of my strengths play out while at Turing, and I now recgonize those strengths and capitil

cbdallavalle

# Challenge 1

I created three divs and floated div1 left, and div2 and div3 right. Then I switched the order of div 2 and 3 in my HTML to get div2 to show before div3. Then I put a small margin-left on to create the space between them.

[Challenge 1] (https://codepen.io/cdallava/pen/qPowMx)

## Challenge 2

I created three divs. I floated div1 and div2 left, and floated div3 right. Then I used margin-top and margin-left on div2 to center the box and push the div down from the top and into the middle of the page. I used margin-top on div3 to push the box to the bottom right corner. This created a small space between my div1 and the webpage, so I used margin -.8% to pull the div back into the correct position.