Tuesday, November 09, 2004

Aftermath

I was recently thinking about the consequences of my actions and how, for the most part, I don't take the time to consider the possible aftermath. And I thought to myself, "Self, what kind of word is 'Aftermath' anyway?" So, I looked it up on Wikipedia and found the following definition:
The word "aftermath" is used more generally to refer to the effects that follow catastrophic events, both man-made and natural. It is almost always used in a negative sense—that is, the deaths from exposure to radiation in Hiroshima are seen as a part of the aftermath, but the liberation of the prisoner of war camps in Japan following World War II would likely not be referred to as "aftermath."

So, that got me thinking, "Is there such a thing as 'Beforemath' or 'Duringmath'?" I decided to come up with my own definitions:
The word "beforemath" is a technical term, used commonly by programmers, when they think, for just a brief moment, that they can solve a difficult equation without the use of mathematics. That "brief moment" could possibly include, but is not limited to, working for 2 or more hours on hundreds of lines of code before admitting defeat. Stupid math.*

The word "duringmath" is also a technical term, used commonly by IT managers, that describes the foreshadowing of the rage and destruction that will occur as a result of a programmer having to delve too deeply into mathematics to solve a difficult equation. See "beforemath".

*"Stupid math" comment is editorial, not part of the definition.
-->