Argh! This is what I get for letting my guard down academically. My project is fucked up. So very fucked up. Either:
- it was one tremendously large bug that I'm completely not understanding
- I have exposed one tremendously large bug that is completely not my fault
- it has 3 or so significant bugs
- I'm just completely lost and should scrap about 500 lines/15 hours of code and just start this freaking mess again -- which I don't have time for
We're 1 week away from the project. I've mailed 4 different mails to my prof. With no response. I can only assume, since he's a normally responsive guy:
- everyone in class is having this problem, and he thinks it would be better to talk it over on Monday
- I have so completely baffled him that he doesn't know WHAT to write back to me
- he's discovered a bug in his code
- for some unknown, inexplicable reason, he's blowing me off.
The last one is unlikely... but usually he checks his email and writes me back in about 24 hours. We're going on 24 hours from the first mail at this point...
I know I should mellow out... but right now the project is about 1/2 complete, I expected about 3/4 to be done this weekend, so this is a big let down. I keep trying to tell myself that since I blew the grades out of the water at midterm time, chances are if I'm not getting it, no one is getting it. But that is cold comfort after 15 hours of not getting The Clue.
- it was one tremendously large bug that I'm completely not understanding
- I have exposed one tremendously large bug that is completely not my fault
- it has 3 or so significant bugs
- I'm just completely lost and should scrap about 500 lines/15 hours of code and just start this freaking mess again -- which I don't have time for
We're 1 week away from the project. I've mailed 4 different mails to my prof. With no response. I can only assume, since he's a normally responsive guy:
- everyone in class is having this problem, and he thinks it would be better to talk it over on Monday
- I have so completely baffled him that he doesn't know WHAT to write back to me
- he's discovered a bug in his code
- for some unknown, inexplicable reason, he's blowing me off.
The last one is unlikely... but usually he checks his email and writes me back in about 24 hours. We're going on 24 hours from the first mail at this point...
I know I should mellow out... but right now the project is about 1/2 complete, I expected about 3/4 to be done this weekend, so this is a big let down. I keep trying to tell myself that since I blew the grades out of the water at midterm time, chances are if I'm not getting it, no one is getting it. But that is cold comfort after 15 hours of not getting The Clue.
no subject
Date: 2005-12-04 09:35 pm (UTC)no subject
Date: 2005-12-04 09:43 pm (UTC)no subject
Date: 2005-12-05 04:07 am (UTC)Zen hugs.
no subject
Date: 2005-12-05 03:01 pm (UTC)Second - how are you at operating systems? And how fast do you read? This is the end of a project, and the problem encompasses both the 1000 or so lines of code I've written recently as well as another 1000 or so lines of my professor's library code. The problem is occuring where "operating system" meets "hardware", so what I need is someone with some insight not only what operating systems should do, but also what this specific hardware is doing in response.
If I don't have insight after class tonight, I might take you up on the offer.
no subject
Date: 2005-12-05 03:07 pm (UTC)I don't promise to be able to find the problem, but I will take a look.
no subject
Date: 2005-12-05 04:35 pm (UTC)Will send you code tonight, if class wasn't helpful. Have laptop with me, but shouldn't play with it during work hours.
You certainly WOULD know plenty about o.s.es! :)