Beefy Boxes and Bandwidth Generously Provided by pair Networks
good chemistry is complicated,
and a little bit messy -LW
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??

Hmmm - before writing a lick of perl, I considered myself a very experienced C/C++ programmer, and a beginner Java programmer. (Of course, you'll have to take my word on those.) Now I consider myself an experienced perl programmer (although you can form your own opinion on that from my track record). I do believe that my background in C, C++, and, especially shell scripting, all contributed very highly to learning perl quickly and becoming useful in it.

I do believe that I am one of the more effective perl programmers in our entire work group, and that I got that way partly from my C/C++ experience. That is, I learned to program, and then I learned some languages afterwards.

I suppose the key to me is someone who likes to learn idiomatically. Who likes to write C in C, Java in Java, C++ in C++, shell in shell, Fortran absolutely nowhere, and will then likely want to write Perl in Perl. I suppose the tough part of this is figuring out that the candidate is such a person - asking this question point blank is useless as most people will understand what the desired answer is and give it, even if they don't really understand the question. Figuring out a behavioural question for this is going to be interesting.


In reply to Re^2: How much time to become a good Perl programmer ? by Tanktalus
in thread How much time to become a good Perl programmer ? by szabgab

Title:
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 How to display code and escape characters are good places to start.
Log In?
Username:
Password:

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

How do I use this?Last hourOther CB clients
Other Users?
Others wandering the Monastery: (7)
As of 2024-04-24 07:18 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found