In my experience, a Junior Programmer isn't responsible for higher level abstraction. In a larger programming environment the junior programmers are given individual components and the senior programmers are expected to stitch the parts together and work on the core api and coding. What all that means to individual Perl programmers is up to you. In my opinion, there are people who can kick out good code but can't be trusted or expected to design complete systems. Call it experience or ability, some people aren't able to put together larger, complex code systems but can write a perfectly good script or module. Senior vs. Junior is more about design ability than coding ability.

--
$you = new YOU;
honk() if $you->love(perl)

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.