3 ms·
> What if more developers developed a sense for the “maximum” number of things a product should do — and stopped there? Then what? Follow this line of reasonin
by satvikpendem 4y ago
> What if more developers developed a sense for the “maximum” number of things a product should do — and stopped there?
Then what? Follow this line of reasoning to its terminal (or shall we say, maximal) conclusion: developers would be laid off or fired (or at best shifted to another product, which might not be what makes money for the business, so back to an increased risk of being laid off or fired). Tell your boss that the product is done, no more updates needed, and see how well it goes for you.
We already know why feature creep happens, people need to work to survive. One of the few ways to prevent this occurs in open source, where people's livelihood is (generally speaking) not tied to their output. If we want feature creep to stop, we would have to live in a society where people wouldn't need to work to survive. I'm sure that will come with AI automation soon enough, if ChatGPT and Stable Diffusion and other adjacent programs are anything to go by.
- bruce511 4y agoYou are correct to frame this in economic terms. It is very much an economic issue as much as a software issue. Assume for the moment you had a sales driven model, like say Word did in the era of those screenshot. Your whole business depends on more sales. Developers, support, admin - stop selling for a month and the business goes under. More customers means more support, which means more overhead, which means sales has to increase in pace. This clearly isn't sustainable (so, no one gets support.) Part of those sales goes to existing customers. (upgrades). Which means new features. It's a treadmill to dream up new things just so there are things to sell as part of the upgrade. Recognizing this route could only end in a crash we switched to a SaaS model. Now support is a priority (and we'll funded), programming, and random new features less so. Customers get better support, programmers get rewarded for fixing bugs, new features can be considered, well planned, and done properly on a decent time scale. And if the business never sells another copy, it's OK. Support remains funded. It's a much better model for customers, for support and programmers, and ultimately yes, better for business owners as well.