Community inquiry solicitation: Code improvement suggestions

Question

AS the title of this thread implies, I am interested in improving the way I program. While continuing to work on a project, I found myself reaching back to old entry-level tricks learned early on to posit a solution to a problem.
however, I am interested to know what you old-hands have done to bring yourselves to a professional level and high quality of output such as robustness, compactness, etc.
Any input is welcome. I would not assume anything about me however as I am but a student so not much to expect there.

Answer 1

Always Learning wrote:
YoungWinston wrote:
Yup. Heartily seconded. In fact, picking up a copy of JUnit and getting into the practise of setting up test harnesses for every class you write will probably help to bullet-proof (or at least rotten-egg-proof) you in the real world of unreasonable managers, expectations, deadlines and budgets.
This is interesting because it is something I do not do often and I suppose if a company creating door lock modules for an automobile will manufacture a test harness, I agree with it is the same process.No idea what you are trying to say, however...
- I am certain that car locks are tested.
- They are probably tested before insertion into the car.
- They are probably tested automatically.