Meeting number 2 is over with.  Our plan is looking pretty good. I've done some check ins with perforce, added our proposed schedule to the wiki and doled out some assignments. Christos and I have already posted which tests we intend to do and Gabriel is on track to finish his picks this evening. I've sent out an email to follow up on the meeting and we should be all set.

Still not much of an effort to be seen from Dan.  I sincerely hope this is a case of a breakdown in communication and not a case of failure to act. I included some instructions for him in the group email and I hope he follows through.  I already feel as though I've failed him as team lead, so i really hope it works out for the best.

We had our first team meeting yesterday. Dan still hadn't touched base but sent an email just after the meeting had concluded about his hard drive crashing.  I think we're experiencing first hand what Keenan had described where when you don't hear from someone you assume they aren't working. I'll have to bring this up during the meeting today to ensure the team is clicking.

I feel like the plan for next week and the wiki is coming together nicely. Today's meeting should go smoothly and I think we'll be all set. I'm looking to do the following function tests:

1. WriteBytes 2. TestReadBuffer 3. UZipDotNet:Compare 4. ReadSymbol.

I'm looking forward to our meeting today.

Just finished Homework 2 and it feels good to get some more perforce experience. In my previous perforce classes I hadn't dared to try out branching and merging and things like that. In general I followed one line of logic and tweaked and fixed as I went. Not much experimenting going on there so it's good to see what this software can do. I'll most certainly be using this in the future.

There were a couple of parts where I had problems and they mostly seemed to be related to my transition from being primarily a C++ programmer trying to deal with C#. At first I didn't have the new classes as their own files. I declared them in line with the main program. I think once I realized the semantic difference here it wasn't hard to cut and paste the classes into their own files and add to perforce. The language itself isn't too hard to pick up though. One of the other obstacle I had here was the fact that in C++ the idea of pointers has really been driven into my skull. It is difficult to adjust away from this and trust that the language will take care of me. A couple of times I wasn't exactly sure how to sort it out so i called a variable a ptr and used it similarly.

Perforce isn't difficult when you're the one taking care of everything. I can definitely see how down the road when we're combining files from different programmers this could be a bit hellish. let's hope my code review skills are up to the challenge.

-AP

Rough Start

As per usual homework was tough to get started after a couple of months off. To make matters work I'm working full time again, which means time is slim. luckily, this weeks homework wasn't too difficult, especially for what I expect from a Keenan class.  As he's stated in class this one should be a lot easier coding wise.  I am happy to hear we'll be learning from some real world experiences.

As for the homework itself I procrastinated hard, but it didn't take long to get done. I had some trouble figuring out exactly how to deal with the args and take in a string. After some quick googling I was able to get the code in.  I had to use the properties menu on the solution and enter in the arguments there rather than from a command line as I wasn't able to get this to work quite right. Hopefully this won't bite me in the butt.  I'll have to make a note to myself to get a better explanation on this.  I'll likely do some experimenting this weekend as well to test a few things out.

I'm officially up and running.

-AP