[tucaz]

I think this is key when you are working with code you don't touch every day.

On code you touch every day one can easily make changes since everything is fresh in one's mind.

When you are working with a code base that you touch once a week or even for a few hours/minutes every day having notes about what you did, why and perceived next steps at the time is crucial and VERY useful.

Another strategy I found useful is to try and be consistent with your choices even if they are not fantastic.

For example: all your tables are named like tbl_entityNam. Even if prefixing every table with 'tbl' is a bad idea, the consistency in keeping it will be useful later when you need to work with that code.