3 ms·
"over time software should converge on being bug free" Yeah, and the way that's done is by refactoring things, removing buggy/deprecated things, and not adding
by md8z 5y ago
"over time software should converge on being bug free"
Yeah, and the way that's done is by refactoring things, removing buggy/deprecated things, and not adding any more new features/requirements... So, pick your poison, I guess? I'd love to go move on to the next job as much as the next person, but somebody still has to be paid to do those things. I don't see what the significant difference is there with free-with-paid-support, if you pay for it up front you're still paying the same cost.
- hsn915 5y agoAll I hear is excuses. I'm not interestd in hearing excuses.
- md8z 5y agoThat seems dismissive and I don't know why you would be hearing that. If there is a way to do this that you think would not qualify as an excuse, then you should mention it, otherwise both of us are stuck to what we are limited to by these bodies that require rest and sustenance.
- hsn915 5y agoYou're creating a false dichotomy: we can either add new features, or stabilize the current version, but we can't do both! Yes you can. You can spend some time to stabilize, and then add new features on top, then stabilize again if needed.
- md8z 5y agoI am not saying that's a dichotomy, I mean this purely as a function of resources. Sure you can do both but that takes up twice as much time as if you only did one of them. So however much you want to do of either is really up to the project's management goals and what the customer is willing to pay for...