Or would you say that the difference is that one understand all parts of Perl but object-orientation? My feeling is that there really can't be anything such thing as a Junior programmer in Perl. Any such individual is safer called a "Cargo-cult programmer" or "cut-and-paste-programmer" and by-and-large you spend more time fixing their code than you would if you just wrote the code from scratch.
Also, I think there is a serious difference between a software developer and a software designer. To date, due to the nature of the job market, I have been forced to be both designer and programmer.
I have bought a few books on Design Patterns and OO Modeling, but I really never feel comfortable with the software architectures I create.
Currently, I am working for a dot-com which has hired out a major software architecture design firm to actually build the site. This is cool because they already have a framework for the Perl code I have to write --- I just have to write it.
In reply to What is a Junior Perl Programmer? by princepawn
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |