|
No, I work for a contractor at a utility company.
|
|
|
|
|
I am sure every heard of the "ID ten T" error?
Spelled out: ID10T
Not acronyms, but the two funniest error messages in my carrier, are based on the confusion they caused.
On the old PDP/11: "Maybe you no run on right system?"
and many years later, there was a SPOT the code should NEVER get to. We don't like silent errors, so this one bubbled up:
"Houston, We have a Problem!"
Unfortunately, it popped up during an install in Texas. And the COMPETITOR had a big office in Houston. Panic set in, before we could explain...
Fun!
|
|
|
|
|
From the car world:
FORD: Fix Or Repair Daily.
LOTUS: Loads Of Trouble, Usually Serious.
ALFA: Aging Latin F*ckwit's Ambulance.
BMW: Break My Windows.
FIAT: Fix It Again, Tony.
JEEP: Just Empty Every Pocket.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
FORD - Found On Road, Dead.
|
|
|
|
|
From Central Virginia --
FORD -- Found on the Richmond Dump
|
|
|
|
|
F'd over rebuilt Dodge - don't forget that one
|
|
|
|
|
One I use alongside TODO and HACK:
|
|
|
|
|
I used these two just this morning. I was donating platelets at the Red Cross.
After the first bad stick, "In for a penny, in for a pound".
When the phlebotomist moved to the second arm, "Measure twice and pierce once". They seemed amused at the time.
Others:
When in doubt, spell it out. (Yes. I programmed with COBOL)
RTFM - Read The F@#king Manual. (When manuals were thin enough to read).
Doesn't anyone use SNAFU anymore? Or is this meant to be a more esoteric list?
|
|
|
|
|
I use SNAFU and FUBAR both. Still.
|
|
|
|
|
|
The 7Ps would have saved a bunch of work throughout the years: Proper Prior Planning Prevents Piss Poor Performance!
It Is The Absolute Verifiable Truth & Proven Fact
That Your Belly-Button Signature Ties
To Viviparous Mama.
|
|
|
|
|
Oh! 7 Ps. We only used 6...
We're philosophical about power outages here. A.C. come, A.C. go.
|
|
|
|
|
LMGBTYOT - Let me get back to you on that
was one of our standard replies when undergoing Software Process certification
emilG
"Dealing with failure is easy: Work hard to improve.
Success is also easy to handle: You've solved the wrong
problem. Work hard to improve." - Alan Perlis
|
|
|
|
|
One of my personal favourites is Recto-Cranial Invert. It means the same as a**hole, but sounds almost medical. 
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
A scary number of moons ago, I was playing in a university (field) hockey team. One of my teammates, with some justification, called the umpire a "myopic catatonic". He got away with it because the umpire didn't understand.
Cheers,
Peter
Software rusts. Simon Stephenson, ca 1994. So does this signature. me, 2012
|
|
|
|
|
Lou Holtz, the old football coach, says, "I would agree with you but then we'd both be wrong."
|
|
|
|
|
I never worked at IBM, but have been told that they have this "official" term "TF", for "Temporary Fix". The "temporary" element sometimes was so flexible that some fixes were internally referred to as "PTF" - Permanent Temporary Fixes.
|
|
|
|
|
|
IBM - Inferior But Marketable
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
If you've got a copy of the original Ted Nelson scrapbook that introduced the 'hypertext' concept (this was in the late 1970s), Computer Lib / Dream Machines, there is a long list of IBM deabbreviations. My copy is deep down in a pile in my basement, but of those I rememeber (without digging it up) is 'Itsy Bitsy Machines' and 'It's Better Manually'.
|
|
|
|
|
FUD - fear, uncertainty and doubt - an old IBM acronym.
|
|
|
|
|
Most Intelligent Customers Realise Our Software Only Fools Teenagers
Association Produces Profit Losing Entity
Produces Erroneous Numbers Through Incorrect Understanding of Mathematics
Will Install Needless Data On Whole System
and of course
I Blame Microsoft
|
|
|
|
|
addMethod.Invoke(m_columnMappings(ordinalColumnPosition).ColumnProperty.GetValue(dataObject), {objectValue})
Taking data from excel named ranges into List<> properties using reflection 
|
|
|
|
|
An expert of programming and C# with some 25+ years of experience in software engineering wrote a really useful function:
private string EncodeFlags(EventType _eventType)
{
if (_eventType == EventType.Alarm)
{
return "A";
}
if (_eventType == EventType.PreAlarm)
{
return "P";
}
if (_eventType == EventType.Malfunction)
{
return "M";
}
return "";
}Already this function alone is some kind of WTF.
But let's look at the definition of the input parameter which he translates:
[Flags]
public enum EventType
{
None = 0,
PreAlarm = 1,
Alarm = 2,
Malfunction = 4
}So he translates an enum with a Flags attribute to a string, ignoring the fact that they are flags, in order to store that value in a database eventually.
 
|
|
|
|
|
He has a bug in in code by not returning a useful defalut value. And its also missing in the enum.
If he is an expert in Solitaire I may know him?
Press F1 for help or google it.
Greetings from Germany
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
