As aniseed alluded to above, this is exactly the wrong attitude. If he were new, that would be the best reason to do right the first time, even if it may be, at first, a little harder. It is still much easier than doing it wrong first, and then attemtping to "relearn" it the right way, which will then lead to hundreds of responses in future threads of the style "but I have always done it this way ...." arguing that the good advice he is getting is wrong, because it does not fit his style of bad coding.

The comment above is just like when someone suggests a newbie should use a IDE for development and shouldn't worry about how the stuff is actually compiled and jarfiles referenced because the IDE will do it for him. Then, two weeks later, that same newbie is filling up forums because he can't compile/run his "application" to run outside of the IDE, or he now no longer has access to his IDE and now doesn't know how to conitune. Or, there is a problem in his GUI (or something), which he let the IDE generate the code for, and he has no idea how to go about fixing it.