I agree, every professor I've had for programming courses has told me to work on the smallest increment that I can find, and make sure it works and you understand it before going on.

The problem that I've been struggling is that I have a hard time seeing the small parts, I want to see the whole right away. I've tried to fix this problem by working on small, generic functions (since taking a few OOP classes), and that's seemed to help me a lot. By working on the smaller functions, I tend to find bugs quickly.

Arashi

I'm sure Edison turned himself a lot of colors before he invented the lightbulb. - H.S.

---

---

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

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, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

Outside of code tags, you may need to use entities for some characters:

	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.