Proprietary code is named that for a reason. I've never had anyone ask for something that they shouldn't see, and I wouldn't show them anyway.

For the last interview I went to (didn't get the job), I asked if they wanted to see any code samples, and the guy said "I saw your CPAN directory, and my developers know your name, so I guess you pass." That's the way to do it I guess. :)

For the job I have now, it started as "I've seen your stuff on usenet, and I'd like to talk to you." Not everyone's boss reads usenet though. Randal does though (and a hint to the people who been asking if Stonehenge has any work: you end up talking to me, but it's a lot easier if Randal has seen you enough in the various places he hangs out that he remembers your name ;)

--
brian d foy <bdfoy@cpan.org>

In reply to Re: Code Samples and Previous Employers by brian_d_foy
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.