Skip to main content

Comp410 > Fall 2007

Sign In

|

Help (new window)

Fall 2007

Fall 2007 > J12 11-16-07 > View Response #13

J12 11-16-07: View Response #13

Name	Dave Eng
Milestone Status: Gains made (If possible, include hyperlinks to what you mention here.)	My milestone status can (finally!) be found here. There's not much more to be said about it other than to reiterate the new changes - Aaron's taking over groups and we're going to continue working on access control - in fact I shall do so until the next milestone, whence I shall fully divert attention to UI.
Milestone Status: Obstacles Encountered	The biggest obstacle was definitely balancing workload. It cut into a lot if not all of my time as well as the time of people I needed to work with. Oy gewalt. Compound this to a lack of time on Friday (friggin' SAS shows) and a really-not-feeling-so-good-although-bearable-now weekend leads to a waaaaaaay late milestone status, and a less-but-still-very late journal. Suffice to say I'll be glad to be home soon.
Milestone Status: Proposed Solutions	There are a lot of things to be said here, but to be fair I believe they would be better addressed in the development section, and thus they will be written there.
Development Process: What seems to be working and why?	Um. This week nothing was working on my end. Well, very little to say the least. We (and I in turn) got a break for the customer meeting due to some other hangups, but that's certainly not a good sign, nor position to be in.
Development Process: What does not seem to be working and why?	So there are a lot of things to be said here - these are mostly gripes and I do acknowledge that there are easily had solutions in the following section. Firstly, when I or Hubert or anyone sends out an e-mail, I really cannot stress the importance of having some sort of confirmation that it was received. Even if it's just an "I got it", it really helps. Aside from that, waiting to meet some one in person in class to get a response is really impractical, and can result in up to 2 days of unproductivity. When we're waiting on some one for some sort of response, it's realllllly easy to use that as an excuse to get other work done - a direct result of this is highly inbalanced workloads between classes (although I do recognize that there are certainly a lot of professors who believe it should be this way, and in their favor). We don't need an excuse to not do work for this class, nor become complacent in any fashion, even if it is productive in some other way. Communication lines in general are awful this week. When Corey mentioned to me that he hadn't heard from me in a while - um...that's definitely a bad thing. When an important section of code is reliant on two people with ridiculously stuffed workloads for the week, it's not good by any means at all - on the other hand, everyone else I'm sure had plenty on their respective plates, so I don't think there was much other option. Having such an unsuccessful week right before the Thanksgiving break is bad. We need to make sure we stay on top of things, for this week and the next. We've yet to have a noodle-fight, noodle-tourney, noodle-siege, noodle-ANYTHING! What gives?
Development Process: Proposals for change--issues addressed and why the change will help.	Here's the listing part. This is the easy part. This is a two parter: Please, please, please send some sort of response or acknowledgement that you've received an e-mail or plans or whathaveyou. The sender should also not get complacent! We have a contacts page! We must learn to use it! Oof one of the hardest parts this week was balancing all of the workloads. This was an extreme situation and I feel that I've performed poorly on several fronts. But just as important as reflecting on the last week is putting that reflection and showing improvement on both next week - and in any other situations like this that may come up. That is why we take this class after all, not as a source of cheap labor (well...I guess there is that too), but to learn. Better here than in a less mistake-friendly environment. I should have stayed on top of my communication, with Corey, with Matt, Brad, Aaron, and...well, a lot of people. That was entirely my fault. This all falls under the communication issue again - we need to make use of the contacts page, and furthermore expound on any issues or problems that have come up, be they technical or not. Matt and Brad shouldn't know that we have a problem when we next have class, they should know when we have a problem. I'm leaving on Tuesday, but I'm going to make myself available up until Thursday - I'm not going to be available then or the day following. Come on guys, nothing beats a bad week like a damn good rebound! As for this one...well...what's the damn hold up? Now for the hard part - the doing.
Peer review: Positive or negative feedback for other class members	Hubert, Jee Yun - glad you guys got malloc done!
Additional Comments	Late; -20 pts. --Chelsea