Completing a 1% job 10 times is much easier than completing 1 10% job.
There is however an Internet sixth sense - that says "dodgy".
A two page site with a email collection form mailchimp is waaaay more forgiveable than something that reeks of pump and dump
Group 1 always produce low quality junk that triggers our 'dodgy' alarms. Group 2 always worry about producing something that is polished and finished.
The secret is to be in Group 2 but to have someone next to you shouting "Ship It!" as regularly as possible.
Too thin - pump & dump. To big volume - group 2. Small, but thick - good shit.
If you are entering an already pretty saturated market then you are probably going to struggle for customer attention without looking very slick.
«The first 90 percent of the code accounts for the first 90 percent of the development time. The remaining 10 percent of the code accounts for the other 90 percent of the development time»
- I didn't stick to the specs
- Added specs while coding
- Didn't test while coding
- Didn't fix shitty while coding
Within the last 10% are small details pushed aside as the pace was chugging along for the other 90%. Seemingly trivial problems are hidden until the end, during which, developers/engineers are most eager to move on to the next mentally stimulating new project.
I think there is a reason why in schooling, 'A' level work requires a completion of that last 10%.
What happens when you haven't thought your task list through is that you tend to add items that required to support the MVP's feature list. I actually find it pretty easy to avoid the features that I've decided have to wait for a later version.
I guess some do it as a way of gaining attention and free advertising.