3 ms·
Interesting take that this is down to software developer sensibilities. My initial thought was that it was due to shooting for as big a market as possible in th
by gary__ 13y ago
Interesting take that this is down to software developer sensibilities. My initial thought was that it was due to shooting for as big a market as possible in the hopes that it would increase chances of success and non tech people would fall just as easily into the 'trap'.
- iancackett 13y agoValid point, and I definitely see biting off more than I can chew as part of the problem. But I suspect architecting (in a lean way) for that bigger market, whilst hitting a smaller niche, may be the balance to be struck.
- jtheory 13y agoThis crossed my mind as well -- you start with a specific problem to solve, you dig into building a solution... and realize that whoa, with only a few tweaks this could be useful for this whole range of related problems... But the compromises add up one after another, and by the time the general solution is built (with an immense theoretical target market), it's lost its heart. The people with the original problem won't be interested any more (because it doesn't speak to them anymore). It's related to the problem of implementing every feature and permutation that users request ("no problem; we'll add an option for that in the settings!"), until the elegant solution becomes an unusable monster. It's hard to say "no" to an addition that clearly adds value, but if you're aiming for a sharply-defined target, you've got 1 degree of "yes" and 364 degrees of "no".