dmarakaki.blogspot.com
Daniel's ICS 413/414 Engineering Blog: Code review: The Good, The Bad, The Ugly
http://dmarakaki.blogspot.com/2008/10/code-review-good-bad-ugly.html
Daniel's ICS 413/414 Engineering Blog. Wednesday, October 22, 2008. Code review: The Good, The Bad, The Ugly. First off I needed to come up with clever title for the blog and I thought The Good, the Bad, and the Ugly was appropriate for reviewing code. I would like to mention that in no way is the title a reflection of my fellow classmates' programs. I will however, point out what I thought was specifically good, what was generally bad, and make a general statement about what was ugly. For (int i = 1; i.
anthonymdu.blogspot.com
Anthony on Software: November 2008
http://anthonymdu.blogspot.com/2008_11_01_archive.html
Contributing thoughts and expanding knowledge in software awareness. Monday, November 24, 2008. DueDates 2.0 Wicket App. One of our group members made a very nice calendar describing our jobs during the span of two weeks. This made it easier to see what we had planned ahead of time and what things were tasked to who. The breakdown of the project was very clear. Each set of tasks were derived from these milestones:. R1) Support an XML configuration file. R2) Basic DueDates functionality. Support libraries...
atshum.blogspot.com
atshum Engineering Log: October 2008
http://atshum.blogspot.com/2008_10_01_archive.html
Thursday, October 23, 2008. I reviewed the projects of Team Purple. At first, I was a bit hesitant to comment on their programs- after all, I don't know anything more than they do, so who am I to be making suggestions? Method to suppress the stack dump and only print out the error messages. I also got some ideas on how to better test our system by looking at their test cases. Daniel Arakaki, Yasu Kaneshige, Vincent Leung, John Ly, Robin Raqueno and Tyler Wolff reviewed our (Erin and my) project. That log...
atshum.blogspot.com
atshum Engineering Log: The DueDates Project
http://atshum.blogspot.com/2008/10/duedates-project.html
Sunday, October 19, 2008. Well if you're like me, then the answer is never- I rarely use libraries (despite working in one), and who goes to the video store anymore? But apparently, it must happen all the time to some very influential people, because I and the rest of my ICS 413 class are working on a project to tackle precisely this problem. The eventual goal is to create a software system that:. Provides multiple user interfaces (e.g., command line, web). Retrieves item, due date and related information.
danmarakaki.blogspot.com
ICS 413/414 Software Engineering blog: October 2008
http://danmarakaki.blogspot.com/2008_10_01_archive.html
ICS 413/414 Software Engineering blog. Thursday, October 30, 2008. Code review: Learning from others. DueDates version 1.1. Gets reviewed by the other development teams in class. Team Purple was assigned to review Team Blue's DueDates. And assess their version 1.1 code and documentation. The class, also was assigned to evaluate Google Project Hosting's code review tool because of issues from the previous Code Review. Due dates. The comparator is defined as an anonymous nested class. Were not too critical...
dmarakaki.blogspot.com
Daniel's ICS 413/414 Engineering Blog: October 2008
http://dmarakaki.blogspot.com/2008_10_01_archive.html
Daniel's ICS 413/414 Engineering Blog. Thursday, October 30, 2008. Code review: Learning from others. DueDates version 1.1. Gets reviewed by the other development teams in class. Team Purple was assigned to review Team Blue's DueDates. And assess their version 1.1 code and documentation. The class, also was assigned to evaluate Google Project Hosting's code review tool because of issues from the previous Code Review. Due dates. The comparator is defined as an anonymous nested class. Were not too critical...
dmarakaki.blogspot.com
Daniel's ICS 413/414 Engineering Blog: Code review: Learning from others
http://dmarakaki.blogspot.com/2008/10/code-review-learning-from-others.html
Daniel's ICS 413/414 Engineering Blog. Thursday, October 30, 2008. Code review: Learning from others. DueDates version 1.1. Gets reviewed by the other development teams in class. Team Purple was assigned to review Team Blue's DueDates. And assess their version 1.1 code and documentation. The class, also was assigned to evaluate Google Project Hosting's code review tool because of issues from the previous Code Review. Due dates. The comparator is defined as an anonymous nested class. Were not too critical...