3 ms·
That's why I gave this talk: intuition says that writing tests for personal projects would slow you down and make you less productive. But I've found the oppos
by simonw 4y ago
That's why I gave this talk: intuition says that writing tests for personal projects would slow you down and make you less productive.
But I've found the opposite to be true! My capacity for personal projects dramatically increased after I started habitually writing tests for them.
It turns out tests aren't just useful for large projects with multiple contributors: they enable horizontal scale for small projects with a single contributor too.
- mberning 4y agoDefinitely helps with having the confidence to pick something back up and start working on it again without worrying about breaking stuff.
- senko 4y agoAs someone who doesn't do this as much as I should, I agree. On projects that are well covered with tests, I find I'm less afraid to pick it back up again and start working on it, because I know there is less chance of some missing context I had in my head months ago and now is forgotten and my change will break the app. Most of my small projects have automated deploys using ansible, not because I couldn't do the deploy manually (in most cases it's ssh to the server, git pull, run migrations, collect static, restart the server), but because with ansible I don't need to remember the manual steps. I am sorely lacking in the documentation area tho :-) Your post prompted me to try to improve there, as I can definitely see the benefit.