zackforbing

MVC in Rails: The Model-View-Controller Framework

One of the hallmarks of Module 2 at Turing is learning the MVC, or Model-View-Controller Framework. Learning the ins and outs of this framework will help a budding developer become a more effective architect of his projects. This sat well with me, as I discovered in Module 1, when one of my biggest weaknesses on projects was knowing where to begin. The MVC is essentially a design template for Rails, as it dictates three different types of objects and how they interact with one another - Models, Views, and Controllers. Each component has a distinctive job in Rails, and their appropriate handling and separation will help you create code that is cleaner, more portable, and more maintainable.

If the MVC thought about iterms of the request/response cycle, it might be more appropriately named the CMV model, as the request cycle goes from the browser to the controller, then to the model (and database). once the data is acquired, the controller passes the data to

zackforbing

Team Members: Garrett Smestad, Patrick Wentz, Zack Forbing

What went well?

we worked really well in a trio, with everyone contributing. there wasn't really any conflict in the group, and we were all very committed to producing a quality product in the end. git workflow went well too, with only very few conflicts to manage.

What didn't?

patrick drove a lot, and wanted the rest of us to take a little more of a lead. getting distracted by small issues that one of us should have solved on our own.

zackforbing

Setting Group Expectations for Rush Hour

Group Member Names: Zack Forbing, Garrett Smestad, Pat Wentz

1. When are group members available to work together? What hours can each group member work individually? Are there any personal time commitments that need to be discussed?

It seems like we will all be able to work as late as necessary and as early as necessary. the only conflict was tonight Garrett had to leave so we are all brushing up on ActiveRecord.

1. How will group members communicate? How often will communication happen, and how will open lines of communication be maintained?

zackforbing

Project workflow: WHY:

0. Load/Reload waffle.
1. Choose a card from the backlog in waffle. If we're working separately, it's best to move that card that you've chosen into ready and perhaps assign it to yourself as well.
2. git checkout master
3. git pull origin master
4. run rspec
5. Checkout a new branch and tag it with #issue_number
6. Write the feature test associated with your waffle card.
7. Run rspec, and make sure that there are no errors that blow up the stack (missing ends, forgetting capitalization, etc.)
8. commit your feature test

zackforbing

How The Web Works

Today we are going to investigate the way the web works.

Materials:

• First let's read MDN HOW WEB WORKS.
• Next let's watch a few quick examples of how the internet works.
• And [how IP addresses work](https://www.youtube.com/watch?v=KFooN7Mu0IM - how IP addresses work).
• Finally let's tie these things together and watch a video about DNS - what happens when you type an address into a web browser.

zackforbing

Module 1 Week 3 Diagnostic

This exercise is intended to help you assess your progress with the concepts and techniques we've covered during the week.

For these questions, write a short snippet of code that meets the requirement. In cases where the question mentions a "given" data value, use the variable given to refer to it (instead of re-writing the information).

zackforbing

Zack Forbing's Turing School Prework

Task A- Practice Typing:

• screenshots of scores will be posted in comments

Task B- Algorithmic Thinking & Logic:

• screenshots of completed sections will be posted in comments

Task C- Create your Gist: done!