How do you explain a race condition to a non-technical person?
retained text
I have been given a task that cannot be achieved without resolving a race condition. The race condition is an inevitable reality of poor architectural decisions where multiple 3rd party applications have the ability to make changes to a shared resource. My proposed solution heavily restricts each app to ONLY write to the resources it manages. Managers raise concern because its a change to how things are done. I've explained you can't work with these race conditions and the managers (non technical) told me they don't know what a race condition means. I've drawn up examples with stick people. "Here is a stick person. Person A calls him 'Bob' and Person B calls him 'Jerry'. Who should he respond to?" Didn't land. I've said "This architeture is like two parents who booked their kid to 2 different classes taking place at the same time because they don't talk to teach other since the divorce." I got a laugh but I was still told by him that he doesnt understand me. Are my metaphors stupid or something? I've really tried and i'm at my wits end. Am I missing some critical principle when communicating technical problems to non-technical people?
document fetched 2026-10-15 00:27 · canonical https://reddit.com/r/ExperiencedDevs/comments/1x5mb8p/how_do_you_explain_a_race_condition_to_a