hmm, i'd like to propose a new jargon item: apocalyptical programming: writing code as if there's no tomorrow, especially not the sort of tomorrow in which you'll have to maintain the piece of garbage you've just written