[edoceo]

No excuses. I've done this like 12 times as startup CTO.

The habit is important. If you don't start, after three pivots you'll have a huge mountain of tests for a system nobody understands. Plus all the wasted time manually "testing".

Tests are so critical for the success of the business. It's fiscally irresponsible to skip.

[mewpmewp2]

What about side projects that you are working alone on?

[niloc132]

I find them vital for side projects - especially if they get set aside for a week/month/year, I sometimes will lose track of assumptions I’ve made or use cases for apis that tests tend to expose.

Sure you can encode all of that as comments, but unless you reread each file when you return from a break, you can’t always trace those thoughts and see where they lead. On the other hand if you “find all references” in your ide or change some implementation so that a test breaks, past-you can save the day with that extra information about what they intended at the time.

[RadioactiveMan]

I really value tests on projects I work on alone because the work is usually intermittent. I don't have the time or energy to deal with regressions, and I may not remember everything about the system by the next time I work on it.

I also find manually testing to be tedious, so I'd rather spend that time writing code that does it for me.

[edoceo]

Well, I don't skip those (but, I started my career (95) in test). I think that it would be OK.

But if the objective is a professional output, test, test, test.