3 ms·
Yes it's actually quite an awkward point for me at the moment. I have a side-project that I've been developing for a while. My attachment to it means that I k
by adwf 13y ago
Yes it's actually quite an awkward point for me at the moment. I have a side-project that I've been developing for a while. My attachment to it means that I know every single bug and flaw within the product. But at the same time I know that if I add caveats to any marketing (it's a bit alpha/beta, etc.), then it will come across as unconfident. On the other hand, if I just say it's amazing and will change your life, I'll probably (can't resist the language even now...), do far, far better.
- jacques_chester 13y agoI know how you feel. The way I deal with it is to find the claims I can confidently make and stick with those. A lot of the time you can do that by looking at the business value side of things. For example, I can't truthfully say that my code is bug free or the best or whathaveyou. But I can say "My product improves <business problem>." I guess the trick is to have two hats. The first hat is the problem domain hat. This is where you make confident, accurate claims about your product. The second is the solution domain hat. This is where you park your professional anxieties about whether you've crossed and dotted everything.