Ask HN: For a startup, when should I begin writing tests?
3 by hazz99 | 2 comments on Hacker News.
Hello! We're building our MVP and have got commitments from our first few customers. I'm still young and haven't managed production software before, only personal projects. I'm hesitant to sacrifice developer velocity for tests. I believe product agility is a huge asset early on, and I think testing cuts into this. I'm also afraid of digging an inescapable hole of untestable spaghetti code and tech debt. I'd love to hear the thoughts of more experienced engineers and founders on this issue! How did you balance it, and what would you have done differently? When should I start testing? My current idea is to skip testing, and instead put that effort into product development and a robust deployment pipeline with easy roll-backs. Ideally this would allow us to move quickly and revert any big mistakes, without the burden of a complex test suite. If it's important, we're React+Go, but I'm not looking for stack-specific advice.
0 Comments