Las siete etapas del programador de Perl

[Marcelo E. Magallon]

Hola,

Seven Stages of a Perl Programmer

by Tom Christiansen

Novice

   1. Thinks CGI and Perl are interchangeable terms.
   2. Still thinks Perl looks like bad C code viewed over a noisy modem.
   3. Is insecure about the concept of dollar signs.
   4. Thinks Perl should be more like sh or tcl.
   5. Has heard of the ``Unix mindset'', but hopes it's a treatable condition.
   6. Can't figure out how to read input from the keyboard.
   7. Thinks regular expressions are somebody cursing.
   8. Wonders why no one can give him a straight answer about whether Perl is compiled or interpreted.

Initiate

   1. Has begun to learn about $_ -- and doesn't like it a bit.
   2. Thinks -w flag is a waste of time.
   3. Thinks Perl should be more like C++ or Java.
   4. Is still trying to figure why Perl has two different kinds of arrays.
   5. Knows how to use perlbug, but sends in bogus bug reports.
   6. Has been bitten by implicit context conversions, but hasn't caught on yet.
   7. Can't keep == separate from eq, and thinks that + should concatenate strings.

User

   1. Thinks Perl is just for text processing.
   2. Uses the Perl debugger.
   3. Has used other people's modules.
   4. Wonders what an object is.
   5. Knows their way around CPAN.
   6. Knows the difference between local and my.
   7. Uses <DATA>.
   8. Is still trying to figure what references are for.
   9. Thinks Perl should be more like scheme or eiffel.
  10. Submits real bug reports with perlbug.

Expert

   1. Write JAPHs to impress their friends and annoy their coworkers.
   2. Begins all programs with use strict.
   3. Thinks Perl should just be Perl.
   4. Has taken enough advantage of cryptocontext to annoy others.
   5. Knows how to create records and objects with hash refs.
   6. Uses syscall to get at undocumented operating system calls.
   7. Curses the flexibility of the Perl object system.
   8. Uses /e in substitutes.
   9. Has begun to wonder what typeglobs are for.
  10. Has written their own modules in Perl.
  11. Begins to look at all data in terms of regular expressions.
  12. Understands why regexes can't match nested data.
  13. Rewrites minor utilities in Perl.

Hacker

   1. Writes games in Perl.
   2. Has written extension modules in C.
   3. Uses AUTOLOAD and closures in curious ways.
   4. Appreciates the aethetics of the Schwartzian Transform.
   5. Delights in the flexibility of the Perl object system.
   6. Has written their own pod2XXX translator.
   7. Understands the output from Perl -Dflags.
   8. Accesses the Perl symbol table directly.
   9. Submits bug reports with working patches.
  10. Edits files using a special Perl-embedded version of vi or emacs.
  11. Has contributed modules, manpages, and tools to the standard Perl distribution.

Guru

   1. Can answer any Perl question instantly.
   2. Can write anything in Perl -- and does.
   3. Takes advantage of undocumented language features.
   4. Writes code that gives even Larry pause.
   5. Implements opaque objects and compiled regexes using closures.
   6. Can read and understand the output of the perl-to-C compiler.
   7. Embeds Perl interpreters in larger applications.
   8. Has written their own -d:debugger module.
   9. Used object-oriented programming before it existed.
  10. Is debating taking their turn with the patch pumpkin.

Wizard

   1. Is on a first-name basis with Larry's wife.
   2. Has written or rewritten major areas in the Perl compiler or interpreter.
   3. Is thinking about rewriting the regex engine, the memory allocator, or the garbage collector.
   4. Doesn't write games in Perl, because they realize that Perl itself is the game.