I can't recommend Nick Corcodilos' book
Ask The Headhunter highly enough. (He also has a website
http://asktheheadhunter.com) It will help shape your thinking about the interview process. That you phrase it as "prove to my employer" rather than "get my employer to see" is a huge step. Nick says that you prove it by doing the work for the employer in a sample situation. Get a real problem that the employer actually has, and solve it in front of the boss.
As an employer myself, I put a lot of weight on the code samples that I'm shown. I can tell a lot about someone's work habits from their code. I don't care if you're a vi or emacs user, or if you prefer 4 or 8 tabs, but I do want it clear that you care about your 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.