|
Yeah... strongly agreed. You mistook what I said. It's not the "learning" code that they want to see. They want to see that you're taking the time to learn. Once you've learned how to do something, then turn it into a formal but still personal bit of code and use it as an example of your work.
I totally agree on the ideas of maintainable code, elegant design, and polish will set folks well apart from those that don't practice those ideas. Again, the chance to shine in those areas is the demonstrable code you send them when they request it.
Of course, this should be YOUR code... not the code that an employer has proprietary rights to or anything else that would violate an NDA, Covenant not to compete, or ethics in general.
--Jeff Moden
|
|
|
|
|
Jeff Moden wrote: Once you've learned how to do something, then turn it into a formal but still personal bit of code and use it as an example of your work I don't generally have the time or inclination to massage throwaway, toy-project learner code to make it all pretty. That's something I'll do when I do my next project, and typically, that next project ends up being my first attempt at real work with the new knowledge.. which means it's already owned by someone else.
|
|
|
|
|
No time and no inclination... that's fine but don't get mad if someone beats you out of a job that decided to make the time and had the inclination. I'm trying to explain how to win the job. You don't have to take that advice. It's your choice.
|
|
|
|
|
Thanks for your response. I get what you're saying. But not having a cache of personal code that demonstrates my knowledge doesn't mean I'm not learning new things. A constant part of my job here requires learning new things. But it doesn't leave behind any code that would be useful to demonstrate my skills, just a bunch of 'hello world'-like snippets.
And it sounds like you were able to weed out candidates purely through the interview process without seeing any code or syntax. Hopefully my interviewers will be able to do the same.
If you think 'goto' is evil, try writing an Assembly program without JMP.
|
|
|
|
|
We didn't manage to hire anyone because we never got to the code part. The candidates were that bad.
I also agree that just because you don't have a personal cache of code examples doesn't mean that you're not learning anything. But, when a company asks for such a thing as a part of the pre-interview, you need to have one because, in the absence of one under such conditions, you may never get invited to an interview. And, no... I'm not talking about the "toy" code some are speaking of. The internet is full of forums where people ask for help. Solutions to such questions make great examples for a code cache, especially the more complex ones.
Again, I'm not trying to force anyone to see it my way. I've been on both sides of the hiring fence and I'm trying to help folks see it the way employers see it to give them a better chance at being the successful candidate for a job.
--Jeff Moden
|
|
|
|
|
I have always had a code portfolio that shows examples of my code and documentation. All of it comes from code I have written and various places I have worked and none of it reveals company information. Just pull a method from some class that shows how you have solved a problem such as transposing data from object to another or filling a list box. It should be the kinds of things you would do regardless of where you work.
|
|
|
|
|
I would let them know those 2 facts, and ask if there is something else you can bring.
They may simply want to see your coding standards in action.
To me, the appearance of your code tells me a lot about the quality of your code.
It also tells me a lot about how you communicate.
Simply be prepared to find other ways to communicate. Also be prepared to discuss your code review processes, and your bug fix ratios. We strive for ZERO defects after release. But 1 defect in 3-6 months is acceptable. We can guess the stability based on the number of lines of code changed in the stabilization/test period before we go live.
And I find it RUDE to ask for code that belongs to another client!
|
|
|
|
|
Never share previous employers code -- I testified as an expert witness against a programmer that did share code and he got one yr and a felony charge.
Also, as far as writing your own code I made the mistake of writing a working piece of code to solve their problem that they used and did not get hired. I will take their tests but provide no new code unless I get paid. The company was obviously looking for a code fix and not interested in hiring. I was not the first one they pulled this on I later found out.
|
|
|
|
|
Unless you're going to throw together some code quickly for them to peruse, why not just tell them the truth -- you don't have a GitHub repository because your hobbies don't include programming, but rather you have hobbies that get you physically and mentally away from work as you find it yields a better work/life balance for you and helps keep you from getting burned out.
Whatever you do, don't steal code from work and pass it off as yours, even if you're the only one who ever had a hand in writing it.
Fact is, you sounds like you're currently employed, so you don't actually need their job. If they can't work with you on this point, are you sure they're someone you want to work for?
|
|
|
|
|
Ask them for a problem, and solve it in front of the interviewer. If the interviewer doesn't praise your idea, don't even consider applying for such a company.
|
|
|
|
|
I had to do that for a job and a friend of the interviewer stole the code and sold it under his on name and he was stopped by a lawyer (luckily). You can not trust people with private code. I would suggest that you could do some work on a open source project and then give them a link to that. That way you would not be in a position where your past companies would want to sue you over a NDA violation.
|
|
|
|
|
Download a cool sounding small project from the public git hub section. 15 minutes with refactoring and formatting, upload to your private git hub and your good to go.
What's that - there's an ethics test too? Crap.
I'm pretty sure I would not like to live in a world in which I would never be offended.
I am absolutely certain I don't want to live in a world in which you would never be offended.
Freedom doesn't mean the absence of things you don't like.
Dave
|
|
|
|
|
I wouldn't doubt some people do just that. How would they know (until it's too late)?
If you think 'goto' is evil, try writing an Assembly program without JMP.
|
|
|
|
|
Can you get high in a pot hole?
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Especially so if there is a crack.
|
|
|
|
|
Are you reefering to pottery here?
... such stuff as dreams are made on
|
|
|
|
|
Only if there's some skunk in there
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
|
|
|
|
|
I imagine so, but they're hard to find unless of course, you use the Bong search engine.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
you could try gazing into the crystal methods
Signature ready for installation. Please Reboot now.
|
|
|
|
|
or you could ask the magic 8-ball.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
Can you get religion in a priest hole?
|
|
|
|
|
Can you get politics in an a**hole?
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Is your corn hole only good for emitting bad jokes?
|
|
|
|
|
I don't know, but if it's smack in the middle of the road, It'd be easy to fall in...
Anything that is unrelated to elephants is irrelephant Anonymous
- The problem with quotes on the internet is that you can never tell if they're genuine Winston Churchill, 1944
- Never argue with a fool. Onlookers may not be able to tell the difference. Mark Twain
|
|
|
|
|
If you hit the pot hole too hard you're gonna fall off the wagon.
... such stuff as dreams are made on
|
|
|
|