Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • You know they're bullshitting, they know they're bullshitting, she probably does as well..

    How about a few questions like.. "So for the last library you wrote, did it have documentation coverage tests, and hundreds of unit tests.. because it's the norm in perl development these days"..

    or "so when was the last time you went to any talks on your enterprise language of choice, or discussed best practice with the local user group. So whens the next UK conference for $uk_language and are you going?"

    Hopefully you can find quite a few chances to show they are bullshitting - get the boot in when they inevitably have errors come up in QA or fall behind.. "so you reckon your code is so much more reliable and readable than perl - why aren't you done yet, why do we still have bugs, where did this bug come from then?"


    @JAPH = qw(Hacker Perl Another Just);
    print reverse @JAPH;
    • While working for 2 of the named popular companies in the past I can say it really depends of the person who holds the "Lead" or "Architect" rule. It's in their responsibility to: - make sure code quality is good - make sure people working on the code are skilled - make sure people working on the code are motivated and not scared by probably upcoming layoffs. - make sure there is room to enhance skills and know-how within the work or at least financed by the company (i really like the 20% idea at google)
      • I'm pretty happy to hire better people when working as a technical lead. Cleverer people.. perhaps not (see explaination later).

        I've been looking for an additional contractor recently and would have been very happy to take on somebody with better perl and integration skills. My job as lead tech has always been to understand the business and build a partnership with the project manager and generally set out how things should be done. If we have somebody who knows better than me, we're more likely to avoid so

        @JAPH = qw(Hacker Perl Another Just);
        print reverse @JAPH;
        • oh yeah.. clever people.

          Avoid anybody described as a genius..

          Of the places I've worked with a 'genius'..

          2/3 times they have had a non-cs background and reinvented every wheel from cgi query parsing to templating to database abstraction, and usually have very odd ideas about how to organise and name things.

          1/3 the genius had a CS background but still insisted that he could reinvent a better wheel than mod_perl, TT, etc.. yes mugwump I'm looking at your smart arse ;)

          @JAPH = qw(Hacker Perl Another Just);
          print reverse @JAPH;