|
I don't know what the actual protocol is (or if there is even is one!) but, if I were you and for what it's worth, this is what I'd do.
I would send a complete project. I'd try to make it something not too big but it must definitely be something that compiles and runs. Otherwise, you're basically just sending them what indentation style you prefer (and we all know how I feel about that!).
I would try not to send them a group project but, if I had to (like, if I had nothing else), I would. Of course, I would clearly show them what was mine and what wasn't.
I don't know what they will do so I will plan for every eventuality. Besides, I'd feel bad submitting code that doesn't even compile...
Lastly, not only would I tell them what the program is supposed to be doing but... I would tell them why my code is so great! What properties it has--like why it's so easy to use, fix and extend. Why it's reasonably efficient. The more specific, the better. I wouldn't just say, "here's my code. Surely, you can see why it's so good, right?" I'd give them an idea of what kind of programmer I am and how I think because, really, they're not going to scrutinize my code. I'd give them an overview so they know, specifically, where to look. It would also ensure that the good parts of my program won't be overlooked. It would be tragic to show them a fine piece of engineering only to have them overlook it's quality.
Of course, this would make my brief longer then a single paragraph but I think that's a good thing...
|