Hacker News new | past | comments | ask | show | jobs | submit login

this is sometimes a good idea, sometimes not (think Space flight, for example).

The current thinking, probably stemming from Google's design-by-stats methodology is that this scales down to startups, you build something and morph it based on feedback. We used to call that design by committee, but clearly when you give it a new name its a different animal :)

I think what's more likely to have happened is that the problems have changed from things like best way to compress these bytes, faster state machine for this network stream, better LCS algorithm to find my n-gram etc, to problems that involve many social factors for their success. When this happens the only way to find those factors is to involve the social community that is creating them. Often those doing the iteration/refine cycle with the developers are not the same as those ultimately using a product, but when it works, it works well.

Software is seeing a shift towards large scale problems, like making the accumulated history of mankind available to anyone, anywhere; or supporting complex life decisions; or connecting and staying connected with multiple disparate sets of 'friends, etc. These are radically different problems being solved in different ways.

But not every problem is solved best this way.




Join us for AI Startup School this June 16-17 in San Francisco!

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

Search: