Beefy Boxes and Bandwidth Generously Provided by pair Networks
The stupid question is the question not asked
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
I would wave in the operating system knowledge.

HTML and other web browser technologies are on the application (browser) level. Not much os knowledge is needed there, but at least some basic understanding of browsers and client operating systems is beneficial, if not necessary.

As for the back end though, that can be close to servers' os. So depending on the os you're having in use or plan to use in the future (which you don't mention), I'd do some screening in those areas. And here comes the C level very likely. Very likely, because C programming doesn't necessarily have to be system programming, and the same applies to Python. They both can be used productively without much concern to the executing os, especially Python. For Unix-like based back end, I'd definitely check the ability of working with standard documentation, the awareness of POSIX, skills in basic system operations. I'd begin with questions: what did you program in C and script in Python and shell? Which shell was that and why? How much interaction with the os did it involve? Do you think it was a good tool for what you did? Did you miss some functionality? What would make it better, easier, more appropriate for the task? About C: what libraries did you use and why? What compiler? This should give you an overview of who you're dealing with.

In reply to Re: Similarities of Perl and Python? by tomasz
in thread Similarities of Perl and Python? by Bod

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 cooling their heels in the Monastery: (2)
As of 2024-04-26 01:24 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found