(1)Though having two brains on the same project/iteration seems beneficial, it truly isn't... some times. When working on a specific piece of code that we both have no idea how to attack/implement, my partner and I just sit there staring at the computer for a good couple of hours. We tried to fix it, but error just kept popping up. An example of this was the line comment regex. We were at the computer lab and had so many ingenious ways of implementing it... and each one failed. Errors were happening over and over and over... until we got kicked out of the computer lab around 1am. At least theres always tomorrow to have fun fixing it... weeee.
I'm not sure how my partner attempted to resolve the problems, but I like the educated trial and error approach. It eventually worked but took a while to figure out what was going wrong. Reading the code that the professor provides really helps, a lot. Before the project deadline we got the regex to work, so I say it worked pretty well.
I'm not sure what we should do differently next time when we both dont know what to do... go straight to the educated trial and error process??
(2)Another challenge I'll state is the planning a get together to finish the project. Our schedules aren't exactly compatible and definitely do not mesh well. Sometimes we start on the project late at night, days close to the due date, or early in the morning. Well we dont need each other to do the iteration, but having that extra brain with you might help?
We attempted to resolve this issue by knowing each other schedules and planning accordingly, but the times we meet are still not at the best time. We'll use the meeting to find out what we should do later individually to code. Good thing this project is only for 1 class and not all of ours, that would be trouble.
TrackBack URL: http://blog.lib.umn.edu/cgi-bin/mt-tb.cgi/161713