I agree and disagree! :-) I agree that you probably shouldn't have cute names for internal important things ("batman" as an internal server/project name is cut

I agree and disagree! :-) I agree that you probably shouldn't have cute names for internal important things ("batman" as an internal server/project name is cute, but doesn't convey much unless you have a "bat" or "cave" or similar product/service/process). That said, at work, we have "Saint Even". This is a cute name for a common problem in our field -- Eventual (Even) consistency. When Saint Even (Pronounced like "Evan") comes to visit, we know we're going to have to either throw up our hands and accept it, or delve into how to fix it. One time, Saint Even blessed us with a 10 second delay. We decided to accept that one because the effort to fix was too large for the delay... However, we should be able to handle a visit from Saint Even for at least 1-2 seconds... It's also easier to say "Saint Even" (when first bringing up the topic, to be clear it's not a person named Evan), and then later "Even" during the discussion, then "Eventual Consistency"... We also get to laugh at the joy this Saint Even fellow brings us as we often need to collaborate to understand where the error happened / did it overwrite data or just stop a process / how can we better handle it in the future (ideally without forcing master-node reads.. e.g. a better detection/retry)