I would highly, highly recommend tests. The problem with not writing tests is that you think it will save you time, but instead, it will end up slowing your vel

I would highly, highly recommend tests. The problem with not writing tests is that you think it will save you time, but instead, it will end up slowing your velocity greatly as your codebase grows and it becomes harder to discover what specific change broke feature X. You don’t have to write thousands of unit tests. But you should absolutely have a basic test suite with integration tests that give you confidence in a new release. And it will make it easier to hire developers in the future. A good test suite doesn’t slow you down at all, in fact, it speeds you up by helping you identify problems rapidly so you can fix code before it becomes a real problem.