Not sure if this is an unpopular opinion or not, but I wanted to share it based on my experience. First, a little background.
I learned to code by building my first app, Graphite Docs. When I was learning to code, I didn't follow any best practices, didn't test a damn thing. I mean, I tested things manually, of course. But I didn't write any unit or integration tests. As Graphite progressed, and as I had to work on other things, I became a better developer. When working on projects that were not MVPs and not early-stage startup products, I wrote tests. I learned the value of testing.
But as I've been working on my new side project, Perligo, I found myself writing unit tests and becoming frustrated by how much it was slowing me down. The product hasn't shipped yet, and every minute I spend writing tests is a minute I'm not spending finishing features.
It took me longer to realize this than I would have liked, but unit tests and integrations tests, while good practice, are altogether useless for a pre-release product. Yes, it will be a little more difficult to add tests later, but no so difficult that I think you (or I) must write them while building an MVP.
Honestly curious if this is a shared opinion or an unpopular one.