This preview is a really great chance for you to go in, and understand someone else's code, and this is a lot of coding. You probably already noticed when you go out, and you look at sample code as you collaborate with other people, and explain to them what you're doing. It's really important to be able to go in, and understand someone else's code, and so this is a great chance for you to learn, and it's a great chance for you to supply the kind of feedback that you want to get in return. So let's take a minute and review the peer review template. Let's take a look at how to fill out this peer review template, and basically the idea is that well, first off, you're going to want to either make a copy in Google Docs or download it as Microsoft Word. This copy is the master copy, and it's not editable, and then you have several different sections which are all noted in here, and you have a combination of quantitative and qualitative feedback that you'll be giving your peer, and so this section here is where you should solve it, quantitative feedback. So look at the rubric, and then if it has all of these things, you put a five here, and so on, and so forth for all these various sections, and then, and this is one of the more important parts, the qualitative feedback goes down here. So try to be thoughtful about how you do this because this is probably the part that'll be most helpful for your peer, and so this first section is about design intents. Did they pick a nice clear set of user stories and wireframes, and did you understand those, and how they related, most importantly how they related forward if you will to the code that your peer created? Second is user experience, is the navigation, and the implementation of that narrative in the user interface, nice and clear, and there's all these sections, qualitative and quantitative feedback there. Then finally there's the code itself, and so does it robustly handle the necessary functions, is it easy to understand, well decomposed, and again I think if you go, your peer probably get the most value out of that qualitative feedback. So that is how to fill out the peer review template, and again this is a great chance to both help yourself by understanding someone else's code which is very much a part of the coding process, and then also to just follow good rule, and supply the feedback that you would want to get about your submission. All right. Good luck and I think you'll enjoy reviewing your peer's work.
