you should also decide whether you want this 6 months contract to be extended, so that you can calculate the "adjustment" and "learning" time

Yes - perhaps I should have included that in the original question.

I am hoping that this will become a permanent position. Naturally, subject to cultural fit, work ethic and actual skills. However, it is also dependent on his ability to make contributions that either generate revenue or free up enough resources elsewhere for revenue to be generated. Right now, I'm not sure that will be the case. I have some plans and ideas of how that might be possible but there are a lot of ifs...

On Python: I would be really worried if a candidate managed to persuade me to convert to using it!

No chance of that!!!
One thing I know for sure is that, until I find a business need for something that our current technologies cannot support, no new technologies will be added! An example of that is the little bit of Java we have. Perl cannot (easily) be used to create an Android app so we had to use Java of Kotlin. Java was chosen because it is more universal and because I did a little Java programming at university. But it's spread is strictly limited to being used for Android apps and nowhere else.

We will not be adopting Python!

I will second tomasz's suggestion that unix-skills are important

I will be digging into what they have done with a Raspberry Pi. This was on the CV and will give me an insight into unix skills.


In reply to Re^2: Similarities of Perl and Python? by Bod
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":



  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.