View this PageEdit this Page (locked)Attachments to this PageHistory of this PageHomeRecent ChangesSearch the SwikiHelp Guide
Hotspots: Admin Pages | Turn-in Site |
Current Links: Cases Final Project Summer 2007

Michael Cook

I am a second year CS major. I just finished my second Co-op term with Synovus Financial in Columbus, Georgia. I am not sure what I want to specialize in yet. However, I do know that I want to take at least one networking class. I am also interested in learning more about SQL databases and Visual Basic .NET since I have used those previously in Co-op terms.

Future Dream:



Extra Credit - Articles

When Bugs Become Features - http://www.jnd.org/dn.mss/when_bugs_becom.html
A common saying is "That's not a bug, that's a feature!". Sometimes when people find bugs in their design, they simply put it in the manual and label it as a feature. The better solution is to fix the bug. The example used is a door that has the same types handles on both sides and only opens one way. I chose this article because it is common practice to try to hide bugs or make them look like features instead. This saves time (which is huge when you are taking other classes that have other homework/projects). But it also doesn't eliminate the problem, which would be the ultimate solution.

Commentary: Human Error and the Design of Computer Systems - http://www.jnd.org/dn.mss/commentary_huma.html
Sometimes human error is used as an excuse of why something didn't work. The truth is that humans are prone to making erros, so how can we deal with this? The solution is to design around human error. Spend time designing solutions to human errors by making them less serious or detecting and stopping them. Here is why I chose this article: One thing I remember being mentioned in one of my CS classes is never to trust user input. Not only could the user have a sinister intent but the user could simply make a mistake. The fact is that human error is not going anywhere, so we have to learn to deal with it as CS majors.

The truth about Google's so-called "simplicity" - http://www.jnd.org/dn.mss/the_truth_about.html
Google's home page is simple because it is hard to find more advanced options. To do somthing other than use the standard search bar requires finding the catagory it is under and searching through possible choices throughout different pages. Other search homepages look complex but are easier to use becuase they clearly present the available options on the homepage. I chose this article because I was running out of good choices and CS majors use Google a lot. It is a very helpful search engine. However, the article shows some of it's usability flaws.

Co Web Assignment 1

Mini Java-to-Squeak Tutorial
Since I am familar with Java, as I am sure many others are, this case is particularly helpful with getting into programming in Squeak. It contains code conversion examples including assignments, logical operators, and loops. A couple key differences are: := is an assignment operator in Squeak as opposed to = and the logical operators used in Java (such as &) are just one character in Squeak (such as &). I would suggest people either take notes about this page or bookmark it so they can go back to it easily. I know I will be going to it a few times as I start programming in Squeak.

Proper CRC Card Creation
Since CRC cards are going to be new to me, I thought I should at least get a glimpse of how to make a CRC card. This case explains how CRC cards are different from UML. It shows a picture of a bad CRC card and comments on how it could be imporved. It then shows a "proper" version of the same CRC card and explains how it is better. The idea the case stresses is to not overcomplicate CRC cards so they can be easily understood by people.

How To Complete Your First Milestone
The title of this case sounded interesting so I looked at it. It has some useful pointers for getting started in Squeak, including how to find classes and methods. The case shows how to open a new morhpic project so you can keep everything for a project in one place. It sounds like this could be a good idea once I learn more about using Squeak. Possibly the most helpful information in this case is having this link: http://minnow.cc.gatech.edu/squeak/. This site looks like it could continue to be useful throughout the class.

Video Professor: Because reading is HARD.
I don't know about other people, but I learn best visually. This case has some very useful videos that show you how to do a number of things. I recommend this case to anyone becuase it shows things visually. A couple of the features I found most useful are: how to file in and how to swap the alt and control keys so you can control-c and control-v like normal programs.

Team Modulus Cases
The first page of this case is somewhat useful. It gives an overview of the importance of design, CRC cards, and UML. The How to test page I found very useful. It gives step by step instructions (inluding pictures) of how to not only install SUnit in Squeak but also how to set up test cases and run them. This information can be helpful if you want to get a head start on writing test cases or to just supplement the eventual lecture on SUnit.

Co Web Assignment 2

Refactoring
Scoping

Co Web Assignment 3

Extreme Programming
Object-Oriented Programming
"Objects do the work. The work is done in instance methods in the appropriate class. Good objects have clear responsibilities and clear interfaces."

Links to this Page