Perl work at Monash

[David Dick]

Agreed that it is to specific to www stuff.  Perhaps also to SQL.  An 
alternative might be talking to complimentary protocols/languages/rfcs, 
such as ftp, snmp, ldap, instant messaging stuff such as Jabber, or 
things like Expect.  Maybe a senior developer and/or architect would be 
capable of the equivalent of writing mibs or ldap schemas by hand, or 
very familiar with 2 - 3 rfcs or something like that. :)

Timothy S. Nelson wrote:

>On Mon, 8 Sep 2003, Nathan Bailey wrote:
>
>  
>
>>1) Would be interested in general comments (i.e. from everyone) on the
>>"Perl career progression" at:
>>	http://polynate.net/work/perl_career.html
>>    
>>
>
>	Looks good.  The only "problem" is that it's specific to your 
>field/job (ie. something more general would be cool).  
>
>	I remember seeing something similar on a Perl training mailinglist 
>years ago, where they were asking the question "what should we be teaching to 
>create (eg) a junior perl developer".  But it wasn't in that lovely concise 
>table format :).  
>
>
>---------------------------------------------------------------------
>| Name: Tim Nelson                 | Because the Creator is,        |
>| E-mail: wayland at smartchat.net.au | I am                           |
>---------------------------------------------------------------------
>
>----BEGIN GEEK CODE BLOCK----
>Version 3.12
>GCS d+ s:- a- C++>++++$ U++ P++ L++ E- W+++ N+ w>--- V- Y+>++ 
>PGP->++ R !tv b++ DI++++ D+ G e++>++++ h! y-
>-----END GEEK CODE BLOCK-----
>
>
>
>  
>