7 ms·
I couldn't agree more. It's a real shame that the standard is that software is never "finished" anymore. Using a work-in-progress is always problematic.
by JohnFen 3y ago
I couldn't agree more. It's a real shame that the standard is that software is never "finished" anymore. Using a work-in-progress is always problematic.
- kuchenbecker 3y agoRespectfully disagree, I think getting value out of a work in-progress is preferable to the alternative and provides vital feedback to the software builders.
- emanuele232 3y agoi agree with both, "finished" software i think can happen only with small pieces of sotfware, every medium size+ project needs a continuous development
- JohnFen 3y agoAs a dev, I get that. As a user, I very much dislike that software is often in a perpetually unfinished state.
- ezfe 3y agoFactorio is a common example of a video game that is very polished. It could be frozen in time and be considered finished. Yet it receives consistent updates finding smaller and smaller fixes and refining the game even more. How do you reconcile those ideas?
- JohnFen 3y agoWhat's to reconcile? If there are releases that are beyond bug fixing, then it it's not "completed", it's a work in progress.