4 ms·
It certainly fits the startup style concept where you expect the product to take off or eventually "pulled" out from the company by customers. Customers in th
by duxup 7y ago
It certainly fits the startup style concept where you expect the product to take off or eventually "pulled" out from the company by customers. Customers in those situations don't jump on board for a bazillion features (that actually sounds like a headache) rather it is probably just for the core of whatever the product is. If they're not interested in that... bazillion side features won't get them either.
I was working on a ancillary product connected to my employer's main product a while ago. It was barely done, missing a lot of features but they wanted to ship it. I was all "ok but .."..... and the folks who wanted it ate it up. No complaints about all the missing tidbits I was thinking of, not a peep. As far as adoption went, it didn't matter. I probably could have spent a month or more longer on that stuff, but it wasn't what was important to get started.
- jrumbut 7y agoGoing through that process a few times before, I learned about the importance of understanding which among the many equally time consuming ways to build something will give you the best tradeoffs as the product grows (or doesn't). Should a record be updated or a new version inserted? Hard or soft deletes? Creating a column for each setting or have a JSON blob? No one answer is correct for every situation. You can be future proof, ready to implement reporting/backup and restore/power user features when the time comes, or setting yourself up for pain.