The two things that help me the most in this department are:
1) write tests first because then you can write something ugly that works and then refactor underneath passing test coverage
2) expose yourself to other peoples code. My tendency is to stare at my own stuff all day (or other people's unattractive code). A natural place to look at good code is to be quick to open up libraries you are using in a project and rummage through them as the need naturally comes up in your work
1) write tests first because then you can write something ugly that works and then refactor underneath passing test coverage
2) expose yourself to other peoples code. My tendency is to stare at my own stuff all day (or other people's unattractive code). A natural place to look at good code is to be quick to open up libraries you are using in a project and rummage through them as the need naturally comes up in your work