1. What is your direct stake in the project? (tied to your grades? Large monetary investment?)
2. What is your extended stake in the project (manager have lots of connections? Is this industry leading and highly visible?)
3. What are the chances you will succeed if you start work again?
Based on the answers to these three questions (which I know will be difficult to obtain) you should make one of the following choices:
1. Politely refuse to work on the project, saying you've committed to other things and do not want to over-extend yourself.
2. Bite the bullet and fix the project based either on you code or the current mess. (and shut up about things until you're done) Walk away once released.
3. Perform some type of negotiations with the manager: (e.g. extend the deadline (all deadlines can be extended), limit the scope of the release, limit the expectations of you) and schedule a post-release evaluation of the project and your role in it.
I got two semesters worth of credits towards my major. However, those two semesters are now over and I've gotten my grades. I feel like somewhat obligated to help if he can't find anyone else but I have my own stuff to do with a ton of CS classes assigning projects now.
"manager have lots of connections?" - the project is in a different department than my major so it wouldn't help me.
"Is this industry leading and highly visible?" It's up there.
I was talking more industry connections. Nobody gives a damn about your schooling once you've done it, to be honest. If your manager however sits on some boards, or is influential in the people that he knows and interacts with, it may be in your best interests to not burn this bridge.
>Is this industry leading and highly visible?
Then you may want to be able to say that you completed it, even if it means you have a couple of shite weeks, otherwise, you can use it as an answer to one of those wacky "worst experience" interview questions.
From what you're saying, I'd strongly lean towards option 2 or 3. Being in the workforce for a few years now, I can't emphasize enough how much it hurts you to burn bridges, no matter how much you're in the right. These people come back to haunt you in peculiar ways.
Good luck. Just remember you have a lot more to lose in this situation by walking away than you have to gain, from what I can gather.
2. What is your extended stake in the project (manager have lots of connections? Is this industry leading and highly visible?)
3. What are the chances you will succeed if you start work again?
Based on the answers to these three questions (which I know will be difficult to obtain) you should make one of the following choices:
1. Politely refuse to work on the project, saying you've committed to other things and do not want to over-extend yourself.
2. Bite the bullet and fix the project based either on you code or the current mess. (and shut up about things until you're done) Walk away once released.
3. Perform some type of negotiations with the manager: (e.g. extend the deadline (all deadlines can be extended), limit the scope of the release, limit the expectations of you) and schedule a post-release evaluation of the project and your role in it.