I would argue that if one is afraid to make changes to the underlying (structural) code, then that is the time when one REALLY needs to sit down and restructure the code to clarify and clean it up.

Indeed, thank you for following through more fully on my thoughts. (By the way, who let you into my brain? Get out of there!) Just to clarify my original point a bit, when I said:

They fear causing new bugs. This is a legitimate fear, and definitely should be considered.

What I meant was that causing bugs is something one should legitimately worry about, not that changing important code should be feared. I further explained that I like to use test suites to help avoid creating new bugs, but your Meditation touches on another technique that can help. Namely, writing good, clean code in the first place, or doing a shakedown on code that isn't good and clean. Nice Meditation, in any case. ++

---

---

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.