|
Recently my group was asked to troubleshoot an embedded program written by our overseas sister company, which was "never coming up" and their engineers(?) couldn't figure out why. A few seconds of perusing revealed the following in the middle of the program's initialization code:
for (long i = 0; i < 99999L; i++) dlytsk(cur_task, DLY_SECS, 9999);
The dlytsk function causes the calling task to sleep for the specified number of seconds. So the effect of this snippet was to sleep for around 32 years before allowing initialization to complete. One has to wonder what the original intent was (both of the programmer and the manager who hired him!).
|
|
|
|
|
Well, what were they thinking? Something like this, maybe:
"Yeah, this program is so hot, it will hit them the face... right after it surprisingly started, which will not happen in the next 3 centuries. My, that _will_ be a surprise..."
"Oh my dear! The Hardware is not yet warmed up, I need a pause before the final initialization. Let's just copy-paste some example over!"
"Heehehe, hohohooho, muhahahaha!"
"Braaaaaains!"
That seems to be a PEBKAC problem, Sir. Why don't you go and fetch a coffee while I handle the operation?
|
|
|
|
|
Perhaps the code afterward launched nuclear missiles, and the programmers were pacifists? 
|
|
|
|
|
this is obviously to omit problems with the power up settling time because a 100000uF cap was placed instead of a 100nF cap...... DAMN HARDWARE GUYS MAN!!!
|
|
|
|
|
An engineer who was about to leave that company wrote that line for he knew that the other "engineers" there would not be able to find it out.
|
|
|
|
|
The way I see the engineer who wrote it was a genius and all other engineers in the company are morons who can't find such an obvious fault. The engineer might have gone on to bigger better things for sure. Damn with the company that hired the other engineers, fire them and re-hire this guy.
|
|
|
|
|
They were really proud of their Splash Screen!
|
|
|
|
|
"Dude, We should give *Enough* time for people to evacuate the building before the application launches!"
"Just read about a funny thing called FOR loop.. Let me see how long I can make it run"
"Here's a hilarious tweak on the program... don't worry, I'll be deleting it before deploying"
"Dude, what's the longest number you can think of????"
-
Just that something can be done, doesn't mean it should be done. Respect developers and their efforts!
Jk
|
|
|
|
|
|
|
Yeah, I found it very hard to keep a straight face while answering OP. I don't do C#, but I figured any language has to have a descendant of the grey-beard strtol(). Google had the answer before I'd finished typing the question.
Cheers,
Peter
Software rusts. Simon Stephenson, ca 1994.
|
|
|
|
|
You're right. There's a .ToString() missing. I.e. :
string sayii = textBox1.Text.Substring(0, textBox1.Text.Length).ToString();
|
|
|
|
|
Probably a ToUpper as well, to protect against lower-case binary digits. 
|
|
|
|
|
round two[^]
Haven't got the heart to take the original thread any further.
Peter
Software rusts. Simon Stephenson, ca 1994.
|
|
|
|
|
Dropped my jaw when I read that message.
Excuse me for my improper grammar and typos.
It's because English is my primary language, not my first language.
My first languages are C# and Java.
VB, ASP, JS, PHP and SQL are my second language.
Indonesian came as my third language.
My fourth language? I'm still creating it, I'll let you know when it's done! 
|
|
|
|
|
No Excel Application, days before I notice
Retrieving the COM class factory for component with CLSID {00024500-0000-0000-C000-000000000046} failed due to the following error: 80040154
|
|
|
|
|
Duuude, 80040154!
Don't tell me you've never 80040154ed something during you're time!
There are careers out there that are totally build up on 80040154!
That seems to be a PEBKAC problem, Sir. Why don't you go and fetch a coffee while I handle the operation?
|
|
|
|
|
"80040154ed" what is that mean?
|
|
|
|
|
It's the verb form of 80040154, simple past. like talk - talked.
Simple, isn't it? And also quite obvious, as you've already stated when you first posted that error message here.
That seems to be a PEBKAC problem, Sir. Why don't you go and fetch a coffee while I handle the operation?
|
|
|
|
|
What I mean is. . .
What do you mean with this "There are careers out there that are totally build up on 80040154!"
|
|
|
|
|
At a guess: Security & Registration. Try google! 
|
|
|
|
|
I mean _absolutely_ nothing, just like the error messages you posted meant nothing.
I was just mocking about that "obvious" number; you shouldn't take that seriously.
But _if_ I had intended a deeper meaning with the sentence you just quoted, it would be this:
There are some people out there who are writing code just like this "obvious error message". When it comes down to maintenance, no one else could handle that kind of bullsh... horse dung. That's active job security, right there!  So, whenever you stumble upon some messages like these, rest assured: There's a dude with a water tight career. He's roared up to a position where his employer is taking crap like that from him, because he couldn't let him go.
But that's just a interpretation of what I wrote. Hell, if I know what I was thinking all the time, I would at least be a miner god. Or totally crazy. Better not find out.
That seems to be a PEBKAC problem, Sir. Why don't you go and fetch a coffee while I handle the operation?
|
|
|
|
|
"not even" 
|
|
|
|
|
So odd.
Somebody in an online forum wrote: INTJs never really joke. They make a point. The joke is just a gift wrapper.
|
|
|
|
|
 that's actually what the error is referring to... 
...but the user has no idea, they just get a lot of errors saying "not even"... it's "not even" their fault, its when one of our drivers malfunctions
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
