Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl Monk, Perl Meditation

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
In a highly connected, easily searchable world, depending on a resume alone might put you at a competitive disadvantage. You might want to rethink that.

If you happened to Google search me, you would find my CPAN directory and a few other things I've done. Is that good enough for you? This discussion is largely theoretical.

It's more important to me that you (1) know when to ask for help, (2) know how to ask a question, and (3) listen carefully.

Number 1 isn't answerable online, except for people who have few "real-world" acquaintances to ask. For those people, you can get a good idea of number 2. With number 3, you eliminate the real flaming idiots. For everyone else, you face something like Warnock's dilemma... did they listen carefully and understand, or ignore the answer and simply give up?

I don't think that finding a bunch of meaningless "community involvement" in the form of newsgroup blather and such is very significant. I find it disturbing that employers want to base their decisions on something that's easy for them to check, whether or not it actually gives them any real information. How do you manage to hire any decent people at all? I realize you probably get a whole lot of resumes to look through, but that doesn't make me any happier about the situation.

In reply to Re: Re: Re: Resume advice for getting a Perl job by no_slogan
in thread Resume advice for getting a Perl job by blssu

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

  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or or How to display code and escape characters are good places to start.
Log In?

What's my password?
Create A New User
Domain Nodelet?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others studying the Monastery: (1)
As of 2022-01-16 19:11 GMT
Find Nodes?
    Voting Booth?
    In 2022, my preferred method to securely store passwords is:

    Results (49 votes). Check out past polls.