I agree on the importance of always striving to write not sloppy code. It is especially critical if you are building a system which must scale and must be maint

I agree on the importance of always striving to write not sloppy code. It is especially critical if you are building a system which must scale and must be maintained over a long time. Trying to avoid sloppy code is one of the things that can make programming a rewarding if challenging experience. > understandable, testable, maintainable and extensible. Those are all adjectives, just like "sloppy" is. So we must each make the decision as to how much effort we will invest in making code MORE understandable, MORE testable, MORE maintainable and MORE extensible. If the value of any of those properties is 0, then the code is definitely sloppy.