Dirty reads is a classic symptom of scaling poorly. Eventually consistent database writes are fine, but it's a bad look if a user takes an action and then doesn't see the results of their action.

Similar to how every description of relaxed consistency for CPUs starts out by pointing out your own reads always observe your own writes in program order, as if to say, "don't worry, we're not insane."