Day 3: Tuesday, January 14th, 2014ΒΆ

  1. For class, read http://www.codinghorror.com/blog/2009/10/the-xanadu-dream.html

  2. Quiz and discussion.

  3. Any homework questions?

    1. What is ChangeLog, and how do I modify it? Do I use ‘git log’? (No; just edit it with a text editor.)
    2. How and where should I ask questions? At the Piazza site.
  4. Demonstration: git and github; editing online and pull requests.

    (Note: this is how we will be doing code review and HW hand in. Also see GitHub Flow.)

    I will need a volunteer! Basic mousing skills needed, and bravery in the face of the unknown.

    1. Log in to github.
    2. Go to https://github.com/ged-lab/msu-cse491-2013
    3. Click on ‘fork’.
    4. Go find the ‘blog-posts.txt’ file and click on it.
    5. Click on ‘edit’.
    6. Add ‘Hello, world!’ just below the first line of equals
    7. Scroll down and push ‘commit’.
    8. Click on ‘pull requests’ (upper right)
    9. Click on ‘set up new pull request’.
    10. ...
  5. Blog post discussion and signup; see Blog post assignments

  6. Looking at the HTTP protocol.

    Concepts:

    • statelessness: Web browsers send a request, Web servers send a response.
    • permission/authentication-less: by default, the expectation is that you can link to any open page; by default, there is no authentication.
    • open: the HTTP protocol is an open standard that can be implemented by anyone, on either side – no licensing, no copyrights, no patents.
    • coupling: how interconnected things are. tightly coupled vs loosely coupled.
  7. Code examples! (See Day 2: Thursday, January 9th, 2014)

Previous topic

Day 4: Thursday, January 16th, 2014

Next topic

Day 2: Thursday, January 9th, 2014

This Page

Edit this document!

This file can be edited directly through the Web. Anyone can update and fix errors in this document with few clicks -- no downloads needed.

  1. Go to Day 3: Tuesday, January 14th, 2014 on GitHub.
  2. Edit files using GitHub's text editor in your web browser (see the 'Edit' tab on the top right of the file)
  3. Fill in the Commit message text box at the bottom of the page describing why you made the changes. Press the Propose file change button next to it when done.
  4. Then click Send a pull request.
  5. Your changes are now queued for review under the project's Pull requests tab on GitHub!

For an introduction to the documentation format please see the reST primer.