> The tools of marketers (data mining, consumer behavior analysis, surveys, market testing, etc) aren't just a veneer to be applied at the completion of a development project.
I strongly agree with this! If you're working towards a product (and not just a hobby project) then these are crucial requirements. If they can be found out before writing any code, then they should be, since it will save time in the long run.
For me it's also the kind of thing that can lead to costly changes after the fact, which is prone to rub developers up the wrong way. It seems like the principle of phase containment might apply - if you found it early in the development cycle, then it would have been easier to fix.
There are lots of startup founders who do feel a bit sleazy, or like they're just faking it until they make it. You don't give that impression at all!
As others have said below, I think you should push your product a bit. It might not be perfect, but if you can talk it up a bit whilst accepting valid feedback, then you're more likely to come off as dedicated and earnest. People can then trust that the product is likely to head in the right direction under your care.
I strongly agree with this! If you're working towards a product (and not just a hobby project) then these are crucial requirements. If they can be found out before writing any code, then they should be, since it will save time in the long run.
For me it's also the kind of thing that can lead to costly changes after the fact, which is prone to rub developers up the wrong way. It seems like the principle of phase containment might apply - if you found it early in the development cycle, then it would have been easier to fix.