I think the key point in the OP’s statement is “early on” I think unit tests (or just more generally a test suite) is invaluable. But when you’re starting out

I think the key point in the OP’s statement is “early on” I think unit tests (or just more generally a test suite) is invaluable. But when you’re starting out small (1-3 person dev team) and the API is changing so rapidly (we learned something this week we didn’t know last week so that new service now only does 1 thing instead of 5 things), tests can _really_ slow down development. And as mentioned by the OP as well, adding unit tests (or a test suite in general) shouldn’t be too hard once you get a stable API I might be preaching to the choir so to speak, but that’s just my $0.02