This has only the most superficial similarities to tilly's case. It's not about releasing code or contributing to a public forum, it's about taking a couple of pages of code along to an interview.

It should be obvious that I'm not talking about work involving security clearances or explicit NDAs. I'm talking about the kind of work that most of us spend our time on -- data munging, HTML parsing, server monitoring, e-mail manipulation -- all that good stuff. Also, code samples are supposed to be short chunks of code that demonstrate your knowledge of programming concepts like encapsulation and good variable names. There's no need to bring in a complete program, or even complete file.

If someone walked into an interview with a bunch of code that handles money transfers for a major bank, I'd consider that pretty disturbing, but bringing in a snippet of code that calculates the right justification on a column in a PDF for some daily report is reasonable and does no real harm to anyone.

If it worries you, then don't do it, but you'd better find another way to create some code samples then. Hiring a programmer without a code sample is like hiring a writer without reading any of her work.


In reply to Re^3: Code Samples and Previous Employers by perrin
in thread Code Samples and Previous Employers by friedo

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.