my friend and former co-worker, jay flowers developed a strong aversion to our workplace based upon his continue frustration of how stupid we acted. (well, that's my take on it). one of ironies within the irony is that jay came up with these on his own, but he was one of the worst spellers (self-admittedly) i ever met in my entire life; no, he is the worst.
anyway, he used verbiage that was off-the-wall, teaching me phrases such as "the forces", "oral tradition" and others.
since he has left our place where we gather from 9-5 in exchange for u.s. currency, and i have tried to keep his legacy alive and i amuse myself with some of the verbiage i come up with to describe the silliniess of our plight/condition.
i also am trying to find things to post here on a daily basis that document my walk across this this third rock from that star.
so here it is, the 1st in a series of pretty gosh darn funny (at least it amuses me) verbiage i have taken to using around my workplace.
preface: we build software consumed by someone who runs it by a 3rd party 1st. this 3rd party independently tests it before the end consumer accepts it. sometimes, these release get stuck with the 3rd party for a long, long time.
i said today, "there is code to support unit test in the production code".
one of my peers question, "in production, like the users have it???".
"well, released code," i said.
"oh, ok, not in production.", he said.
"ok, well, we released it, let's call it shelf code, then.", i said. and the term "shelf code" was born.
shelf code - noun - code that has left the building, staged to be deployed to the end users, but probably will be in this purgatory for a long, long time.
No comments:
Post a Comment