LogFAQs > #979033900

thisworld posted...

But figuring that out depends on each party's perception about the current situation. Sometimes their perception differs because of the difference in their expectation and past experience about the current situation.

24hrs clock doesn't rely on perception. It conveys the morning/evening part perfectly everytime. 12hrs clock can do this too but people often leave out the AM/PM part for the sake of brevity. Let's go back to post #51 for real example.

My team's reason is obvious so let me clarify my leader's. It's basically:
"C'mon people it's weekend. I'm not expecting you to wake up and go to job during weekend! I mean go, enjoy your weekend, get some rest, have a nice evening. I just asked for a little bit of your time before you go to bed."

My team and leader have different perception about that "9.30". As you can see both reasons hold merit so it's impossible to justify one reason over the other. That "9.30" legit could be interpreted both ways.

24hrs clock simply removes this ambiguity out of the equation.

*shrugs*

One guy who by your own example was the only guy out of an unspecified number who couldn't figure out how this works hardly negates the literal millions of times a day people communicate successfully. Meanwhile, there's no question that more than one guy ever has gotten mixed up trying to figure out what time 20 is and missed the appointment by an hour or two.