

Meme isn't new: it dates to evolutionary biologist Richard Dawkins' 1976 book The Selfish Gene, where it functioned with a meaning other than its current most common one. Unfortunately some processes on a computer can take quite a long time, but it is rare for programmers to advise users that "this will take a long time, and you should take the opportunity to catch up on a good night's sleep".You're right, this needs more cats. A moment is correctly used of a very short period of time, so a few moments would still be a short time, but longer than a moment. I would have left this as a comment but will include this with gave the following comment: Yes it is meaningful. An alternative was ".for up to three minutes?" This is how certain brands serving financial institutions defined a moment.ĭictionaries like Lexico give a moment as "a brief period of time." That may be 1-3 minutes, but we were shot down on saying "about two minutes." Accuracy in minutes for these CSRs defeated accuracy of idiomatic expressions. It was far from idiomatic for me, "1-3 minutes," in the languages I handled, especially English. Having worked in development receiving calls for the rollout of an international financial service assistance center, best practices advised against asking customers to hold "for a moment," the problem retort being, "How long is a moment?" About ten years ago, the jargon was brought to a rather specific, " I put you on a brief hold of one to three minutes?" "A few moments" (or any similar phrase), specifically in relation to software, denotes a passage of time that will take no longer than a few moments. It is actually more meaningful to just tell the user whether this process will be long or short. Because, how would you run a metric on the time that its meant to take? Sure, you can set up check points at specific points of the program or application install, but how are you meant to know how long a specific computer/cpu/gpu/drive/operating-system will take to execute up to that checkpoint.
A FEW MOMENTS LATER DEFINITION VERIFICATION
With minor software installs or programs like a file compression/decompression, or an application install, or a download verification - the ETA is near impossible to reliably determine. I have an interest in software engineering, so I feel like I can answer this quite well. To answer your question specifically, which I have not quite done, you need to understand that 'moment' is a wildcard, used when an exact time isn't appropriate. So, the 'moment' might quantify as 4-5 minutes. Suddenly the context switches from a punctual employee, to a lazy, disrespectful one. Now, lets say this employee is known for being really slack, and disrespectful. In your head, you have just quantified what a 'moment' is. Now as you are the boss of the accounting firm, and currently holding a meeting, you would expect your employee to take roughly 2-3 minutes.

You are in a meeting and one of your subordinates asks to use the bathroom, he says "Sorry, just one moment, I need to go to the restroom". Lets say you're a manager of an accounting firm. Just give me a moment of your time and I'll try to explain it. The use of "moment/s" as a description of the passage of time - is intrinsically defined by the context of its appearance.
