Eventually, one must choose, and specialize in those areas we wish to master. Eventually, we learn to trust the skills of those around us; to rely on the works of others to take care of the nitty-gritty details of those areas in which we are perhaps not so skilled.

Yes, and if you do not choose for yourself, your projects will choose your specializations for you. If you are not very careful, you may find yourself specializing in things you really don't enjoy or care about.

Some solutions, I think are:

• Keep an active eye on the progress of your technical skills and the ones you wish to develop. If you cannot do that in your current situation, then you need to choose between the safety of the known and the risk of the unknown.

• Find ways of networking with skilled peers in the fields you wish to cultivate. This will help you build your technical skills and it will help you learn of opportunities more aligned with your desires.

• Invest in your technical skills on a regular basis, whether taking a few hours over the weekend, attending local user groups, lurking in appropriate technical communities, or whatever.

• Use personal projects to learn the basics of the skill you want to grow. This will help you find time to actually build them. By creating things you care about, you'll be able to maintain your enthusiasm while crawling up the learning curve.

• Prioritize your To Do list and manage that like you'd manage any other project. Give yourself schedules, task lists, and requirements. This will help you develop and/or maintain your design discipline.

• Never stop asking, "How can I do this better?"

The Perl community is really quite fortunate to have such a broad range of talent willing to help others learn. Between the O'Reilly books, CPAN, and sites like the Monastery, it's very easy to find new and better ways of doing things.

I've only seen that type of teamwork in a few other communities and none of had the breadth of support that the Perl community does. If this is important to you, then I suggest you use it as much as you can.

--f

---

---

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.