Congratulations.

This is a good problem to have.

When you have reached the point that you can effectively use existing resources to solve questions that you can, formulate, and if you find yourself actively doing so (so it isn't just a question of thinking you can find answers, but not actually doing it), you are probably making pretty effective use of them. That is what they are for.

However your continued awareness that there are things you are missing is probably accurate as well.

At this point there are a few things which I find helpful.

1. Stretch your boundaries. While you don't have and obvious questions, there are things you probably would find useful to know about that you don't. Make a habit of identifying such areas and trying to learn more. This is useful in and of itself for obvious reasons. However it will also give you lots of specific questions, some of the answers to which will give you context for and clarification on things you thought you knew.
2. Try to answer questions. While trying to answer questions you challenge your own knowledge in a different way that tends to bring out what you only thought you knew.
3. Find out what others think is important. Every subject accumulates basic facts that experienced people all know, which are not obvious to beginners. You probably would never on your own realize that goto poses a fundamental maintainance problem, and never think of programming styles beyond procedural. If you think that there is more you should know that you don't, there is people out there who are perfectly willing to tell you what they think is important. Some of their suggestions will open your eyes.
4. Review what you think you know. How would you say it to someone else? How do you wish it had been said to you? Why does it make sense to do it this way and not that? Why did they choose the way that they did it? The answers are often enlightening...

And remember, questions come in clumps. You might have no real questions for a couple of weeks. Then you rethink something and you have a ton of them until the dust settles.

---

---

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.