An engineering student's lament

Guys, guys,

I am a senior about to graduate with a degree in Computer Engineering, and my final team project is a robot.

However, my team has no fucking clue how to do anything.

First problem... multi-threading the sensory input, everyone either said they don't know how to code at such a low level, or they don't know how to do any multi-threaded code, so I volunteered to do both.

Second problem... networking to a controlling server, everyone said that they did not know how to do networking code, so... I volunteered again.

Third problem... GUI, no one wants to work on the GUI for the server because it is difficult... Guess what happens?

Fourth problem... Logic... detecting the angle of objects requires an intense amount of trigonometry... so...

So what is there to do after wiring the embedded devices, programming the devices, managing the flow of information from them, controlling said flow in multiple threads, processing information in some AI, sending and receiving information with a server and making the server user friendly?

I don't know whether I should rage or baw.

Just rightly get all the credit for the project.

Fourth problem... Logic... detecting the angle of objects requires an intense amount of trigonometry... so...
So what, asshole? If trigging is too hard for you, you might as well give up programming.

Assuming you can accomplish EVERYTHING... do what >>2 says. Speak to your professor (or other responsible superior individual) about the situation.

maybe look for another solution besides doing everything from scratch

>>3
I used a literary device where I let the readers infer with their own intelligence what the possible outcome of the situation was. Of course, if you would like for me to spell it out, I did the wall measurement, path finding, and angle measurement logic as well.

>>3
Are you seriously this stupid? If so, you can't probably understand this post either, so don't bother replying.

>>6-7
YHBT. YHL. HAND.

Also, I agree with >>2.

>>7
YHBT, methinks.

Sounds like every project I've worked on.  Do it all yourself, and you burn out and the team dislikes you for your efforts anyway.  Delegate, and quality turns to shit or things just don't get done at all.  There's really no way to win.

Do it all if you can, but don't forget to delegate easy little tasks, not because it will save you time but because your teammates will feel good about themselves and give you better reviews.

Also, if they're useless engineers but decent people, set them to work on docs and presentation.  Let them make you look good.

no one wants to work on the GUI for the server because it is difficult...
GUI for the server
GUI
server
wut

>>12
X. FREE X. 68.

>>1
If I was on team with a pushover like you, I'd feign incompetence in order to get out of working, too.
So stop whining. At the very least I'd point a couple of them towards some point-and-drool GUI tool, and try to shove them onto whoever is mentoring you, so they can babysit them.

>>12
they should just use netcat

do the whole project yourself.
don't let them steal your credit

Do you use Java or C#?

Why are your team mates so reluctant to learn new skills?

>>18
>>18
>>18
>>18

>>19
>>19
>>19
>>19

++++++++[>>+++++<<].

>>18
You've never worked with people, have you?

>>22
No, I have not. I work with computers.

>>23
and penises

do all the work yourself and at the last minute abandon them and hand it up as 100% your own

Shoot everybody.

>>26

>>25

I'm going through the same thing

I sleep well knowing they don't know what's going on and will look ridiculous when we do our solo writeups

>>25
There is a peer evaluation at the end where you give people a rating between 0 and 100, and this rating is added to the ratings of the other members and used in the multiplicand for the final score given unto each member... That is my only recourse.

>>11
We tried... and at the eleventh hour and the eleventh say of the mid-term budget proposal write up... more than half didn't do everything that needed to be done... I had to make up entire sections of the documentation.

As for the presentations... same thing happened again.

>>29
You give them 0, that's all their lazy asses deserve. If they rate you down, you should seek a higher authority and let them know that they truly did nothing of credit.

Lazy people disgust me. 

Lazy dogs disgust me. I even killed one once, don't remember the name though...

TELL your prof that the rest of the team is in no way competent enough. Also say that you dont feel it's justifiable to be used as their grade bump, and that working in such a slow poke team will hold you back and lower your grade.

If they hit you with the whole "IRL, you can't pick the team you're on" bullshit, politely inform them that this is in fact an academic setting, WHERE GRADES ARE OF UTMOST IMPORTANCE and your career is in fact based on said grades you recive, not who was on your fucking team.

Besides, you'll finish the project in less time because you wont have to coordinate a load of assholes.

Currently using these words in college. My average is up to a H1(eurofag - usa 1.1 or 1st class honours). =D

>>1
Sup, Pseudonym.

used with Windows XD Anyhow I need   to share I   guess SQL too   but SQL is   not that bad   At least with   lisp is painfully   clear what code   they would generate   again nobody is   going to die   but i shaved.

>>32
Its name was Haskell.