in reply to Similarities of Perl and Python?

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

I will second tomasz's suggestion that unix-skills are important. Not only because you indicated before that you have such environment in your host but also because automating and standardising procedures (e.g. procedure to export all files from development to production machines, backup or reinstate DB contents, etc.) is important (to me). Some knowledge of security is also important both for backend and frontend.

Unlike others, I would not consider knowledge of C important or desirable for such a small time-span and for the frontend. Neither I would deem R experience important at all. R is a script-like language but that's it. OTOH both C and R would have taught the candidate how to break things up in small functions or package things in modules. And about data structures which is another thing that I saw your code be in need for, e.g. function return data.

On Python: I would be really worried if a candidate managed to persuade me to convert to using it! That said, similarities of Perl and Python could be the main data structures (hash=dictionary, arrays), knowledge of references (that's where C comes handy, re:pointers but Python references I think are transparent, Perl's aren't) how to combine these into complex data structures, functions receiving and returning complex data structures, extending function behaviour easily as the spec changes (e.g. input parameters), modularising into packages, reading config parameters, testing-testing-testing and, of course, OO. All are really important and are crossing the boundaries of programming laguages.

I would consider also spending some pub-beer-time together as part of the interview. The ability to learn new things and improve depends highly on personality. The ability and desire to automate too. We are talking about comp-science projects after all.

And I am going to cramp here my usual OS-hatred tirade: I would never hire anyone using a specific OS for their home desktop on their free time (and, no, Android does not count). I would demand 24/7 exclusive use of specific OS only ... Yes I am an OSist!

Finally, for such a small timeframe, perhaps giving them a concrete task to solve at home, prior to the interview would be a good indicator. For example: "use Template in order to solve some real problem" you faced, or "use this DB schema to setup database, insert mock data and retrieve it (within Perl)". I don't know how would this work wrt paying them for it as it can take a couple of days of work.

discalimer: I have never interviewed anyone, but had lots of others interviewing me.

bw, bliako

Replies are listed 'Best First'.
Re^2: Similarities of Perl and Python?
by Bod (Parson) on Aug 30, 2021 at 17:49 UTC
    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.

      No chance of that!!!

      noted! just to clarify: I did not mean you specifically

        No, I realise that you didn't specifically mean me...

        I felt it useful to add that we already have a plan for dealing with adding technologies to our existing infrastructure if it is suggested or becomes necessary. Useful to people coming this way in the future if nothing else.