When I hear the term Junior (foo) I tend to think of someone who is going to be working as part of a team, but not in a leadership type position. ie. a person who is just following the specification that was given to him/her by someone else. I tend to think of it in terms or titile/position as opposed to skill level. In this case, the position dictates that they aren't making decisions, just following orders.
The Senior (foo) on the other hand, is the person who has a hand in the decision making process of the tasks. They then pass off part or all of the grunt work to the Juniors.
Of course, this scenario could be adjusted depending upon the size of the organization. Maybe you have Seniors, Juniors, and grunts. The Seniors make the big decisions, the Juniors decisions over implementation details, and the grunts just follow orders.
I think that there are those who may be excellently knowledgeable within every aspect of a language, but can't make design type decisions. And there are those whoe can make excellent designs but aren't guru's within programming. And of course, there are those who are pretty good at both. It could also be seen as a case where it's what you prefer to do as job and not stictly a matter of capabilty.
Since HR has to have a label for the job position, following command heirarchy for labels is perfectly valid, and isn't really a perfect parallel to a person's skill.
/\/\averick
In reply to Re: What is a Junior Perl Programmer?
by maverick
in thread What is a Junior Perl Programmer?
by princepawn
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |