So, always read the terms of service of platforms you intend to integrate into your projects. And do it before you spend weeks or months developing the project :').
* - High risk involves dating, supplements, CBD, and various other things.
This one is worth checking out as well: https://stripe.com/en-mx/legal/restricted-businesses
I missed this the first time around, but it looks like they've also banned "Get Rich Quick Schemes":
"Get rich quick" schemes, including investment opportunities or other services that promise high rewards to mislead consumers; schemes that claim to offer high rewards for very little effort or up-front work; and sites that promise fast and easy money
Interesting.
Not an anti-correlation: I'm not saying bad code is a good business; I'm saying it's no correlation, that it doesn't make much difference either way.
The worst code you can imagine and then some? Business awards and acolades in one case, business went under in another. Latest design pattern, CI, code review? Too slow for market in one case, strong market position in another.
2. There is no universal lessons to learn, or wisdom to apply in every situation. Including the point above. Every complex enough situation is unique. “bad generals prepare for the past war” as someone said.
The idea of the MVP is there to say "publish this as soon as you can, don't wait because the market will have moved on and you'll run out of money if you wait for perfection".
MLP is a reaction against this, but I don't know if it's a reaction by perfectionists (who are wrong because then you go bankrupt), or a reaction by people who've tried one too many buggy and unready alpha products that was shipped to test the market before it was ready (who are correct, I'll let you think of your own example here).
