BobJanova wrote: Programming isn't something you should just hack around and hope something works I actually know a couple of well respected developers that have mastered the ability to "just hack around". A sort of meta-p.o.c. type development. The things that work correctly, stick, while the things that do not, changes until it works correctly. QA/QC would be obsolete if everything worked the first time -which is realistically known as inconceivable. The type previously described is one way to make it to QA. I take a different approach personally but, it really doesn't matter as long as the code functions as required, is maintainable, and is complete in the allotted time. What are "best practices" anyways other than socially acceptable opinions? Don't get me wrong, I do tend to agree with development best practices but when it comes down to it, it is merely an officially accepted opinion on how things should be.