Bring it on disk if you want, but also print the 50 pages of code, prepared to give it to the manager to keep, barring any NDAs or the like. If you can't let him keep some chunk of code, that's fine. He'll understand.
Here's the scenario you want: You whip out the stack of code, with your best stuff on top. Paper clip sections together. Hand him different packets. "Here's a command-line utility that is a grep for image files. I'm really proud of that one because X, and it wound up saving the marketing department 2 hours a day." He thumbs through it, sees that it is well-written code, clean enough to eat off of. Your pride shows. "Here's a module I wrote for tracking ICBMs, using Parse::RecDescent. What's cool about this one is...."
Now, he may go looking at the code if you give it to him on disk. Maybe he'll want to show others in the department. But when you're face-to-face, and you're showin' your stuff, if it's not on paper, chances are he's not gonna see it.
"Show me the code!"
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.