The Final Hurrah, but I won't stop

It took me awhile to think of a title, but this will do after my brain just got fried. This is the final hurrah for the semester, but this does not mean that I am at the end of my journey. Before I talk about my journey, I want to go over my final project.
As a team of four, our project goal was to implement our DueDates 2.0 with Wicket to create a web application for library books. Given two weeks to complete the project, we decided to spend the first few days getting acquainted with Ronn's DueDates 2.0 code and also assigning issues so that we all know what our focus is. Our project started to get rolling once we started meeting up and coding. We made great progress and we expected our project to be done by Friday, but a small road block became the Great Wall of China for us. Everything in the back end of the project seems to be complete, but connecting that with wicket was painful. Ronn was the one who tried to tackle this issue, but it was out fault for not being able to back him up when he needed us.

I think failing this project was the best thing for me. If this project had run smoothly, I would have not learned so much from my team and from myself. Coming into this project, I knew that I was the weakest link (Goodbye). Learning from my previous group (Violet), I built upon my mistakes and tried my best. As a group, we met almost everyday at Sinclair Library to program with each other for a few hours. This really helped us in keeping each other up to date and to resolve and issues quickly. During this project, I went to Ronn a lot because I saw him as the strongest one in the group. I learned a great deal with Ronn's help and I'm truly grateful for his patience. From the group, I was blessed with their great code. I've seen coding tricks that I have never seen before and styles that are more clean and friendly to future hackers on our project.

Over all, we worked well as a group. We all worked our fair share and what was asked of us. There are small issues with merge conflicts, but we resolve it quickly since we programmed together majority of the time. This was due to our willingness to meet with each other everyday for a few hours. The only problem we had was the wicket and how we assigned issues. By dividing the program, we lose sight of the big picture sometimes.

This is the end of our project and a small part of me feels sad that I won't be able to program with Ronn, Creighton, and John. I enjoyed hacking away with these guys even though the project was painful. I am graduating this winter and I am so lucky to learn so much from this group. I'm slowly hacking away at my "program" and I feel that I just knocked down a huge issue.