Week Two

Wow, what a week. That's what I get for waiting until three days before the project was due to start. I kept pushing it further making excuses to myself citing reasons such as other classes and work I had to do for the various organizations I am in. I can tell that, looking forward, I am going to have to organize a little better, start my projects earlier, and work on them piece by piece by adding comments that will help me analyze previous work.

In previous semesters, classes required me to go through terminal in order to run my tests and eventually turn in the projects, but I still managed to work mostly through a text editor on my home machine. I found myself, through the majority of the project, waist deep in terminal-- writing code using nano, editing my tests, pushing to my git repository, and eventually testing all of my solutions. I guess I better get used to this.

Moving forward, looking at the requirements of the next project, I definitely plan to do things differently. After reading through "XP: Installed", I was amazed by the importance they place on testing, but know I see why. Having thorough and helpful tests not only can show you that your solution is performing correctly, but if designed in certain way, can help point you to possible bugs in your code. It wasn't until after I wrote out a few non-trivial test cases that I soon learned where my program was falling apart. Writing exhaustive test cases is critical, and I hope that I have learned my lesson.

Until next time. Rock 'n Roll