Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

In most scenarios I can tell you if I like or dislike a feature much faster than it takes a developer to build it


If it just came down to the "idea guy liking or disliking a feature" things would be quite easy...


why doesn't it? it doesn't have to be you or me personally, it could be a representative sample of our users


So if you wait to put together a representative sample of users and gather the data long enough for the numbers to matter, you’ve gated further changes. If you’ve gated further changes for a week, why does it matter that the feature change was done in an hour or a day?


Releasing it to users does not take a long time. Randomly select 5% of your user base and give them the feature. If your development process was mature, this would be a button you could push in your deployment env.


Deployment isn’t the problem. If you’ve pushed a new version of a feature that five percent of users use per week and you’ve pushed it to five percent of the userbase how long do you need to wait to have reliable data on that before you push another experimental version?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: