Conflict resolution and the inability to come to a business decision on what to do has stopped offline-first support in a couple apps I've done. Its a really messy conversation to have, especially with people that aren't used to sweating the details. You can't just handwave away the complexity!
It doesn’t happen often, until you make e.g. a ticketing system with a pool of ticket handlers that claim a ticket to work on it, instead of a sole ticket handling responsible, and now it happens dozens of times a day and the customer is irate at such incompetent software.
I may at an earlier part of my career, when I knew far less about building robust software, have stumbled into such an experience.
Comments
Conflict resolution and the inability to come to a business decision on what to do has stopped offline-first support in a couple apps I've done. Its a really messy conversation to have, especially with people that aren't used to sweating the details. You can't just handwave away the complexity!
I've seen business software, where money can be lost, just handwave and silently dropping conflicts (because "it doesn't really happen that often!")
It doesn’t happen often, until you make e.g. a ticketing system with a pool of ticket handlers that claim a ticket to work on it, instead of a sole ticket handling responsible, and now it happens dozens of times a day and the customer is irate at such incompetent software.
I may at an earlier part of my career, when I knew far less about building robust software, have stumbled into such an experience.
"We dont need to worry about that because it like a 1 in 100000 chance of occurring"
Proceeds to do millions of transactions a day.
perfect is the enemy of the good, and perfect can be iterated towards as demand scenarios increase