3 ms·

Ship, measure, respond. That really is the not-so-secret sauce.

• swombat 16y ago
  A pretty shitty sauce. Shipping before you have any idea whether anyone wants what you're building is a recipe for building stuff nobody wants. Coding should be done quite late, after validating the market need, that people are willing to pay, etc. Unless your time is worthless, of course.
  • Swizec 16y ago
    I beg to differ, my most successful project to date has been a website I shipped for the sake of shipping, didn't ask anyone if they wanted it, didn't even think too much before doing it. Anyone I ask now whether they want it, they're quick to claim it's a waste of time that nobody wants to use, and yet those same people just can't get their hands off.
    • kolektiv 16y ago
      Beware confirmation bias. History may be written by the winner, but we could probably learn as much if not more by listening to the loser. Because you were lucky in this instance does not make that good advice for others to follow. (I'm not saying it's bad advice either, just...)
      • Swizec 16y ago
        It probably all depends on opportunity cost. If it will take you three months to build something shippable, by all means, be damn sure somebody wants it. When the cost is not sleeping for two nights ... meh, just do it.
  • dansingerman 16y ago
    I expected anyone to tacitly understand that you of course are building something in the first place that you believe has a market, and have _some_ evidence for that. But given that, I stand by the above. You are better off having a product you can iterate on based on real world feedback, rather than a theoretical construct that hasn't been tested.