For me, writing tests and documenting my build / test / deploy process are critical steps. If I don't have tests in place, I have a hard time picking up a project again after a little while away from it, since I can't be sure if it's even in a working state, or if I can get it to a working state quickly.
This usually takes the form of a README with a few example command lines to run.
Additionally, I find that if I put a project aside with a failing test already written, it's easier for me to pick it back up again, since I've effectively already set up a problem for future-me to solve. A friend of mine calls this "parking facing downhill", which I think is a great turn of phrase.
This usually takes the form of a README with a few example command lines to run.
Additionally, I find that if I put a project aside with a failing test already written, it's easier for me to pick it back up again, since I've effectively already set up a problem for future-me to solve. A friend of mine calls this "parking facing downhill", which I think is a great turn of phrase.