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.
  • In the grand scheme of things, Learning Perl (llama) Courses [] have dominated our sales and revenue. My theory is that it's pretty easy to define the "first" step that Perl programmers must take, but the "second" step is harder, because you have to find 15-20 people that are all in the same place, and need to move the same direction. That's rare, and getting rarer. A business needs only a few people who are Perl experts to oversee the throngs of Perl intermediates who can get assistance from (and upgrade t
    • Randal L. Schwartz
    • Stonehenge
  • > Firstly, once people know a technology they're
    > more inclined to continue with self-learning

    This is the correct one for me. When I know nothing about something, I prefer book-style documentation, with explanations, examples, and context (the Llama, Conway's OOP, Chassell's Elisp Intro), but once I have a certain level of mastery, I prefer pure references (POD, manpages, the Elisp manual, source code).
  • I laughed out loud when I read:

    '... many managers view skills in a binary
    fashion: you either know Perl, or you don't. Once
    an employee has completed the basic training they
    have a tick in the Perl box and they don't
    require any further training. It doesn't matter
    if the employee disagrees.'