How do you deal with unfinished software?
2026-05-22 13:02 UTC
Replies (8)
-
@Zahtu@feddit.org 2026-05-22 13:30
if it does not fit my purpose (aka software is unfinished), i will not use it and will not wait for bugfixes. so either (2) or (3)
-
@solidheron@sh.itjust.works 2026-05-22 13:55
That’s kinda complicated. I thought about underdeveloped interface but a perfectly working backend. If it functions but like the interface is difficult than pressing button
-
@Hawke@lemmy.world 2026-05-22 16:40
In general: I would rather not wait. This mostly benefits everyone: user gets to see what is coming, developer gets feedback, and depending on software maybe user can start getting the benefits sooner on the other hand, it has some risks: maybe devs spend time fixing problems instead of bigger “building the system” tasks. Maybe users get attached to the “pre-release way of doing things” even if the final release is better. (Early access game mods can be very vulnerable to this) Complete vs simple software, it depends on what the job is. Some complexity is fine, and some bugs are fine, as long as there is a plan to get to where you want the software to be.
-
@slazer2au@lemmy.world 2026-05-22 17:48
By realising there is no such thing as finished software.
-
@Shimitar@downonthestreet.eu 2026-05-22 14:10
Love Unix principle: do one thing and do it right. So I look for quite stable and simple software rather than huge over complex monsters that are never really finished or ready (yes IBM and Microsoft I look at you)
-
@Tabitha@hexbear.net 2026-05-22 16:10
it’s either fit for purpose or not fit for purpose. “finished” software can be a meaningless treadmill to nowhere.
-
@okwhateverdude@lemmy.world 2026-05-22 17:26
Depends if I have access to the source. If so, robots can iron out the rest of the bits I need
-
@IWW4@lemmy.zip 2026-05-23 22:36
I have been fiddling and much later working in IT since 1985 and i have never seen finished software.