Blog post assignments

Up to two students may sign up to write a blog post about each class day, and each student may sign up for two blog posts total. Each blog post will count towards half a project at the end of the class (i.e. 2 blog posts will satisfy 10% of your grade).

To sign up for a blog post, go to https://github.com/ged-lab/msu-cse491-2013/, fork the repo, edit this document, and submit a pull request to me to merge it back in.

Content

Blog posts should discuss most of the following in ~5-7 paragraphs/400 words minimum:

  • An outline of what was discussed in class;
  • Relevant links that were brought up, and how/why they’re relevant;
  • Your thoughts (including agreements or disagreements) on any opinions expressed by the instructor or by other students.

You can also add:

  • Other links on related topics that you found interesting;
  • Additional thoughts that you wanted to bring;
  • Relevant personal experiences.

Class days

  • [ leflerja ] 4. 1/16
  • [ ] 5. 1/21
  • [ ] 6. 1/23
  • [ ] 7. 1/28
  • [ ] 8. 1/30
  • [ ] 9. 2/4
  • [ ] 10. 2/6
  • [ ] 11. 2/11
  • [ leflerja ] 12. 2/13 - Rich Enbody speaks on security
  • [ ] 13. 2/18
  • [ ] 14. 2/20
  • [ ] 15. 2/25
  • [ ] 16. 2/27
  • [ ] 17. 3/11
  • [ ] 18. 3/13
  • [ ] 19. 3/18
  • [ ] 20. 3/20
  • [ ] 21. 3/25
  • [ ] 23. 3/27
  • [ ] 24. 4/1
  • [ ] 25. 4/3
  • [ ] 26. 4/8
  • [ ] 27. 4/10 -> CTB NOT IN TOWN/CLASS CANCELLED?
  • [ ] 28. 4/15
  • [ ] 29. 4/17
  • [ ] 30. 4/22

Table Of Contents

Previous topic

Welcome to the Web Dev class (2014)

Next topic

Basic Instructions for Git and Github

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 Blog post assignments 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.