After doing the peer review, it made me realized that I need to change the way that I write programs. As I've notice from the two other systems that I've reviewed, there wasn't any testing done at all and require a bit more error handling. Maybe because we're still in school and the first thing we think about is completing the required task first to do what it's intended to do. Since a program that is incomplete will receive a worser grade. We will definitely have to change this mentality once we get into the real working world.
During the meeting, I felt a bit of awkwardness when it came to giving critiques to peers face-to-face. As I'm not sure how they would take my critiques and they probably think the same way. But once we got the ball rolling, it went really smooth as each team was eager to hear how they can improve their codes. It's almost like a teaching and learning experience all in one.
Majority of the critiques that we received had the same issues. They were able to get it to work with the Eclipse IDE, so they couldn't test the codes.We did all of the testing for our program in the command prompt so we didn't know it couldn't compile in Eclipse. When I try running it in Eclipse, I received a NullPointerException, it have to do with us using the "console.readline" to read user input. Other critiques were that we needed more comments to make our code easier to understand. We will be working on these issues and hopefully get it all fixed back this week.
Over all, This peer review was a great experience and an eye-opener for the ways we program.
Subscribe to:
Post Comments (Atom)
0 comments:
Post a Comment