Complete text -- "How to Save Time with Abbreviations"

Posted Monday 14 July 2003

How to Save Time with Abbreviations

Here's a handy tip that can yield big savings:

Use abbreviations. For example, when I operated Network Answering Service in San Francisco, we quickly learned to develop standard abbreviations for common things people say. For example, OOT for "out of town", or WCB for "will call back".

Other handy abbreviations include PLSC for "please call", NA for "not applicable", DBA for "doing business as", DA for "doesn't answer", and OCS for "onward christian soldiers".

But why limit this to written notes? For example, suppose you want to thank somebody for something, but it's just a little thing. You want to thank them a little but not a lot. To communicate this precisely, and to save time at the same time, just abbreviate "Thank you" or "Thanks".

Say: "Thank."

See, that's less than "Thanks."

But wait, there's more!

You can abbreviate more complex ideas, as well. For example, perhaps you were thinking just now that these are the moments of your life, and this is how you are spending them. Well, in this case, you could save some thinking time by using an abbreviation of "moments".

For example, you could say "momo". That would be like one little moment. Or the plural form "momos", as in "These are the momos of our lives."

Often the practice of abbreviation yields surprising insights. For example, thinking about how these are the momos of our lives, you might just naturally think about death. And then of course there would be "no more" momos, and you could abbreviate the "no more" as "nomo".

So you can see, you could speak, or think, very succinctly. You could think about the momos of our lives, and how, when we die, we got nomo momos nomo.

You see how that can save you time?

Now if you just save a few seconds every couple of hours, then you'll accumulate several minutes every single week. By the end of the year you'll have an extra thirty or forty minutes. Over a lifetime you might have hours, or even days, saved up!

And that ain't bad.

Posted by bloggard at 16:48:00 [Link] - Category: 2 Views
Comments

Inhuman Resources wrote:

I just saved three to four hours by trying to computerize a task after the person who designed it left to office for God knows how long. I think if I added more technology I could save one hour of labor for every ten hours spent trying to get the program to work. A goal to add to my performance plan in 2004!
12/31/03 14:09:35

bloggard wrote:

Yes, I'm glad to hear it. And of course, the practice of abbreviation can save lots of time in programming. For example, debugging.

Let's say you have a program and it's written in perl or maybe in the c language, and it's got a complex algorhythm that just won't behave. That is, it always produces the wrong answer.

Abbreviation theory comes to our rescue. First, you ask yourself what is the natural abbreviation for the word "number". Of course! The natural abbreviation is "#".

So, on the entire section that gives poor results, just preface each line with the abbreviation "#", and barring typos, I think you'll find that the erroneous answers will no longer be generated by that troublesome section.

For example, a line like this --

variable22 = 14 * 85 / 46 - 3;

would become --

# variable22 = 14 * 85 / 46 - 3;

There you have it. If other sections of the program are having trouble just add the number abbreviation in front of those lines, too. Eventually, you'll have no further peskky trouble from that program. Pretty much guaranteed.

Abbreviation theory in action!

(PS: For you non-programmers, adding the number sign before a line makes the line invisible to the executing computer, and each program section so treated would in effect vanish, so as to cease causing trouble.)
12/31/03 17:28:09
Add Comments
This item is closed, it's not possible to add new comments to it or to vote on it