Working on my own project as a solo dev, I hardly ever write tests. What I've learnt over the years is that tests lock your code in making it hard to adapt (yo

Working on my own project as a solo dev, I hardly ever write tests. What I've learnt over the years is that tests lock your code in making it hard to adapt (you could say making you less agile). When I'm smashing out new code and I haven't established patterns then it doesn't make sense to lock that new code in. Once I do have a pattern going then I might add tests, but it's not for the sake of test coverage or to gloat that I have tests, it's purely because I actually care about making sure those bits of the code work as intended and that the edge cases are covered. For these tests I do indeed do TDD. Otherwise it's a trade-off - would I rather be closer to a feature people can use or would I rather be slogging away writing and maintaining tests. This being said, I will say that when I come to a point of adding more people to the team tests will become much more important. The way I see it though, not having tests and having people complaining about it means that I've done something right.