Good Sample Code for Interview?
-
What constitutes a good block of Sample Code to give a prospective employer?
I'd blame it on the Brain farts.. But lets be honest, it really is more like a Methane factory between my ears some days then it is anything else...
I'd say your prospective employer might look at your code three times if all goes well: 1.First a quick scan over it: if it looks horrible with no stucture, no spaces, and nothing to tell me whats going on, it's heading for the bin. 2.Second OK, I'm willing to have another look scanning/reading a bit slower this time: Now I at least take time to see whats happening as I scan through. Can I pick up the story? 3.Third, now I'm interested and I might actually look in detail at some of the actual code. As one who has interviewed prospective programmers, nothing puts me off as much as the interviewee pulling a wad of printout and saying "here's something I did whilst working for .....". Are they going to take away all they do here the same way? So when I meet prospecctive employers I ensure I of point out "I've got permission to use this code" or this report; or point out i'ts something I wrote at home etc. And is code just code? I'd be more impressed by an intro saying this code was written based on .... and using a style of .... using .... recommendations. I can see a book "Clean Code" on my bookshelf, refering to such a book, or a standard, is going to make it more than just code, it's already put in the readers mind that you can work to a style, standard or team rules. Good luck.
-
I'd say your prospective employer might look at your code three times if all goes well: 1.First a quick scan over it: if it looks horrible with no stucture, no spaces, and nothing to tell me whats going on, it's heading for the bin. 2.Second OK, I'm willing to have another look scanning/reading a bit slower this time: Now I at least take time to see whats happening as I scan through. Can I pick up the story? 3.Third, now I'm interested and I might actually look in detail at some of the actual code. As one who has interviewed prospective programmers, nothing puts me off as much as the interviewee pulling a wad of printout and saying "here's something I did whilst working for .....". Are they going to take away all they do here the same way? So when I meet prospecctive employers I ensure I of point out "I've got permission to use this code" or this report; or point out i'ts something I wrote at home etc. And is code just code? I'd be more impressed by an intro saying this code was written based on .... and using a style of .... using .... recommendations. I can see a book "Clean Code" on my bookshelf, refering to such a book, or a standard, is going to make it more than just code, it's already put in the readers mind that you can work to a style, standard or team rules. Good luck.