Submitting Code Examples... - Tilted Forum Project Discussion Community

Moskie · 04-16-2004, 06:59 AM

So I'm gathering some code to submit to a place I'm trying to get a job at, and they want some examples of my work. I've done this before at other places, but I'm still not quite sure on what kind of samples I should give, and how much.

Some questions I've had:

Should I give entire projects, or just a few classes from one?
Is it ok that I give them group projects I was a part of (containing some code that isn't mine), and then explain what I did for the project?
Will they actually try to run my code, or just look at the source? (that may be a stupid question, but I'm sure some stuff would have trouble compiling on their end... is that ok/expected?)
I assume I should give a brief description, perhaps a paragraph long, talking what the example is and what it shows I can do. Anything else specific I should say about it?

This is for an entry level position, so I assume this is to just get a feel for my skills, and make sure I at least kinda know what I'm doing. Any tips on how I should do this would be great!

KnifeMissile · 04-16-2004, 02:26 PM

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...

seretogis · 04-16-2004, 10:36 PM

I seriously suggest against sending an entire project as a code sample, if you have any sort of problem with that code ending up in a company project. Code samples are to show knowledge of the language and how clean your code is -- there's no reason to chance having your projects usurped by sending an entire project's codebase.

feelgood · 04-16-2004, 10:51 PM

Don't send the entire group work. ever.

1. Simply because its not all of your work. Even in this case, you still need to ask your group members permission to submit it to the company

2. Companies are greedy. It is possible that they can grab the project code and use it as their own. Since your group may not actually claim copy rights on it yet, you'd be pretty much screwed.

So, I'd recommend sending a small sample of your work and some of the testing process involved in ensuring that the code works, its input, output. Be sure to include documentations such as programmers notes, method description, etc. If possible, be presented when they go over your coding, its easier for both you and them in which if they have any questions, they can ask you. This way, any confusion can be easily avoided, but depending on the details of your code documentation, there should be minimum confusion.

Moskie · 04-17-2004, 06:18 AM

thanks a lot for the responses, guys.

Quote:

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!

great suggestion.

And I'll definately take the comments about submitting group work into account.

04-16-2004, 06:59 AM	#1 (permalink)
Moskie Pure Chewing Satisfaction Location: can i use bbcode [i]here[/i]?	Submitting Code Examples... So I'm gathering some code to submit to a place I'm trying to get a job at, and they want some examples of my work. I've done this before at other places, but I'm still not quite sure on what kind of samples I should give, and how much. Some questions I've had: Should I give entire projects, or just a few classes from one? Is it ok that I give them group projects I was a part of (containing some code that isn't mine), and then explain what I did for the project? Will they actually try to run my code, or just look at the source? (that may be a stupid question, but I'm sure some stuff would have trouble compiling on their end... is that ok/expected?) I assume I should give a brief description, perhaps a paragraph long, talking what the example is and what it shows I can do. Anything else specific I should say about it? This is for an entry level position, so I assume this is to just get a feel for my skills, and make sure I at least kinda know what I'm doing. Any tips on how I should do this would be great! __________________ Greetings and salutations.

04-16-2004, 10:36 PM	#3 (permalink)
seretogis Huggles, sir? Location: Seattle	I seriously suggest against sending an entire project as a code sample, if you have any sort of problem with that code ending up in a company project. Code samples are to show knowledge of the language and how clean your code is -- there's no reason to chance having your projects usurped by sending an entire project's codebase. __________________ seretogis - sieg heil perfect little dream the kind that hurts the most, forgot how it feels well almost no one to blame always the same, open my eyes wake up in flames

04-16-2004, 10:51 PM	#4 (permalink)
feelgood Free Mars! Location: I dunno, there's white people around me saying "eh" all the time	Don't send the entire group work. ever. 1. Simply because its not all of your work. Even in this case, you still need to ask your group members permission to submit it to the company 2. Companies are greedy. It is possible that they can grab the project code and use it as their own. Since your group may not actually claim copy rights on it yet, you'd be pretty much screwed. So, I'd recommend sending a small sample of your work and some of the testing process involved in ensuring that the code works, its input, output. Be sure to include documentations such as programmers notes, method description, etc. If possible, be presented when they go over your coding, its easier for both you and them in which if they have any questions, they can ask you. This way, any confusion can be easily avoided, but depending on the details of your code documentation, there should be minimum confusion. __________________ Looking out the window, that's an act of war. Staring at my shoes, that's an act of war. Committing an act of war? Oh you better believe that's an act of war

04-16-2004, 02:26 PM	#2 (permalink)
KnifeMissile Location: Waterloo, Ontario	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...