I have done a stupid!!!!!
-
Nelek wrote:
at least do it in a criptic way
...and if that was too much to ask for, then one could do it in a cryptic way. :)
"Real men drive manual transmission" - Rajesh.
Well done! you just volunteered for the next valenciano spelling-bee
-
It was so much more fun when it was a physical object - the legs could fall off or anything! :laugh:
Ideological Purity is no substitute for being able to stick your thumb down a pipe to stop the water
OriginalGriff wrote:
the legs could fall off or anything!
You programmed spiders? Kuwel!
Panic, Chaos, Destruction. My work here is done. Drink. Get drunk. Fall over - P O'H OK, I will win to day or my name isn't Ethel Crudacre! - DD Ethel Crudacre I cannot live by bread alone. Bacon and ketchup are needed as well. - Trollslayer Have a bit more patience with newbies. Of course some of them act dumb - they're often *students*, for heaven's sake - Terry Pratchett
-
It was so much more fun when it was a physical object - the legs could fall off or anything! :laugh:
Ideological Purity is no substitute for being able to stick your thumb down a pipe to stop the water
I know what you mean, my attitude for a time was "at least I can kick what I produce when it doesn't work", now it's all Software, more expensive when you kick it.:confused:
-
In a rush to email some code last night, I sent the wrong executable one which contained the following bit of test code
if (txtSerialNumberRead != txtSerialNumber_ReadIn)
{
MessageBox.Show("ERROR!! Kill all humans");
MessageBox.Show("Serial Number Entered Does Not Match **** Attached", "**** Tester", MessageBoxButtons.OK, MessageBoxIcon.Error);
}
//elseThe proper build does not offer death to humanity just the lower message, here's hoping the recipients look at there next mail before running it! Anybody else had this happen, shipped something with a dumb comment not hidden? or is it just me! Glenn
I once forgot to remove a log message from a destructor. The message said "Ahhh, I am dying, who the elephant killed this innocent playlist". Fortunately I noticed it myself next day when I saw the log file filled with elephants. BUT WAIT, this was inside a product, I wonder, if such a log file is still sitting on someones device. huh perhaps(hopefully) not.
-
I once forgot to remove a log message from a destructor. The message said "Ahhh, I am dying, who the elephant killed this innocent playlist". Fortunately I noticed it myself next day when I saw the log file filled with elephants. BUT WAIT, this was inside a product, I wonder, if such a log file is still sitting on someones device. huh perhaps(hopefully) not.
Just wondering the "elephant" in question did not have trunk. Did the whole message appear or just "elephant"
-
In a rush to email some code last night, I sent the wrong executable one which contained the following bit of test code
if (txtSerialNumberRead != txtSerialNumber_ReadIn)
{
MessageBox.Show("ERROR!! Kill all humans");
MessageBox.Show("Serial Number Entered Does Not Match **** Attached", "**** Tester", MessageBoxButtons.OK, MessageBoxIcon.Error);
}
//elseThe proper build does not offer death to humanity just the lower message, here's hoping the recipients look at there next mail before running it! Anybody else had this happen, shipped something with a dumb comment not hidden? or is it just me! Glenn
Yes! I once developed windows mobile app for my ex job (a food wholesales agent) The app was an inventory / shop system. Anyway, one of the features was that they could send orders from the phone to the companys webshop. The web orders could have a custom comment attached. So for debugging reasons I made the comment from the phone app "Tord is a small horse" tord was my co-worker, older humorless guy. Time passed and the app was deployed. One day a sales guy from our company called Tord and asked, "why do our weborders say that you are a small horse?" Apparently every sales person had been seeing the small horse comment for quite some time. And Tord was pretty pissed :)
-
In a rush to email some code last night, I sent the wrong executable one which contained the following bit of test code
if (txtSerialNumberRead != txtSerialNumber_ReadIn)
{
MessageBox.Show("ERROR!! Kill all humans");
MessageBox.Show("Serial Number Entered Does Not Match **** Attached", "**** Tester", MessageBoxButtons.OK, MessageBoxIcon.Error);
}
//elseThe proper build does not offer death to humanity just the lower message, here's hoping the recipients look at there next mail before running it! Anybody else had this happen, shipped something with a dumb comment not hidden? or is it just me! Glenn
A developer once pushed code that had the debug set so no data would be modified. After that debug flags had to be set in the config file.
-
A developer once pushed code that had the debug set so no data would be modified. After that debug flags had to be set in the config file.
Well at least you could set them, Glenn
-
I believe I have mentioned this before, but I once did a demo of a new system and some new functionality for reporting (which had been terrible in the old system) and when the report popped up it said "Elephant you sunshine". The audience was a Dutchman, and Italian, a Scot and a handful of Englishmen. All IT persons, not users or managers. Fortunately those in the room were so blown away by the new functionality and amused by the content of the report. Apart from the Scot who wondered how I had got hold of the letter from his mum.
Every man can tell how many goats or sheep he possesses, but not how many friends.
-
In a rush to email some code last night, I sent the wrong executable one which contained the following bit of test code
if (txtSerialNumberRead != txtSerialNumber_ReadIn)
{
MessageBox.Show("ERROR!! Kill all humans");
MessageBox.Show("Serial Number Entered Does Not Match **** Attached", "**** Tester", MessageBoxButtons.OK, MessageBoxIcon.Error);
}
//elseThe proper build does not offer death to humanity just the lower message, here's hoping the recipients look at there next mail before running it! Anybody else had this happen, shipped something with a dumb comment not hidden? or is it just me! Glenn
-
But that's a feature! Killing all humans is what you want in that case, right?
"I have a theory that the truth is never told during the nine-to-five hours. " — Hunter S. Thompson
You might be right there, definitely users. Here's hoping my opposite number gets to the mail server before the ***** testing the boards do. :java:
-
In a rush to email some code last night, I sent the wrong executable one which contained the following bit of test code
if (txtSerialNumberRead != txtSerialNumber_ReadIn)
{
MessageBox.Show("ERROR!! Kill all humans");
MessageBox.Show("Serial Number Entered Does Not Match **** Attached", "**** Tester", MessageBoxButtons.OK, MessageBoxIcon.Error);
}
//elseThe proper build does not offer death to humanity just the lower message, here's hoping the recipients look at there next mail before running it! Anybody else had this happen, shipped something with a dumb comment not hidden? or is it just me! Glenn
-
I restrict such shenanigans to my comments, so if I forget it's there the customer/non-developer higher-ups would never know.
I used to, then this project a back and forth with my opposite number and that happened. Mind you the backup plan worked thank the....... Glenn I just noticed the reply option is different, a button rather than just a hyperlink in the text (or is my PC going sideways again?)
-
In a rush to email some code last night, I sent the wrong executable one which contained the following bit of test code
if (txtSerialNumberRead != txtSerialNumber_ReadIn)
{
MessageBox.Show("ERROR!! Kill all humans");
MessageBox.Show("Serial Number Entered Does Not Match **** Attached", "**** Tester", MessageBoxButtons.OK, MessageBoxIcon.Error);
}
//elseThe proper build does not offer death to humanity just the lower message, here's hoping the recipients look at there next mail before running it! Anybody else had this happen, shipped something with a dumb comment not hidden? or is it just me! Glenn
The stupid thing was not to send it to the customer, but to write stupid code (or stupid messages) Doing this, you just promise yourself that you'll have to come back and clean it :-(
gzo
-
The stupid thing was not to send it to the customer, but to write stupid code (or stupid messages) Doing this, you just promise yourself that you'll have to come back and clean it :-(
gzo
I completely agree, however silly messages are very useful when tracking down issues. Note things like that from now will commented out with /* & */ and not // as it is too easy to remove the intended comments
-
In a rush to email some code last night, I sent the wrong executable one which contained the following bit of test code
if (txtSerialNumberRead != txtSerialNumber_ReadIn)
{
MessageBox.Show("ERROR!! Kill all humans");
MessageBox.Show("Serial Number Entered Does Not Match **** Attached", "**** Tester", MessageBoxButtons.OK, MessageBoxIcon.Error);
}
//elseThe proper build does not offer death to humanity just the lower message, here's hoping the recipients look at there next mail before running it! Anybody else had this happen, shipped something with a dumb comment not hidden? or is it just me! Glenn
I once programmed a function and added some assertions. For one of those assertions I figured it was impossible to break, or if it were, it must be someone meddling with that code. I considered removing the assertion entirely, but instead added a message box saying: "You shouldn't be seeing this error message. If you do, please speak to <my name>" When we sent a prototype to the client for testing a few weeks later, I promptly got a call, asking about that exact error message! Seems one of my colleagues was messing with my code after all. Only we didn't catch it in testing ourselves... On the plus side, that prototype was meant for testing and weeding out ... if not these kind of stupid messages, at least the cause for it (which was a real bug). Also the tester found it rather entertaining. :)
-
I once shipped a debug build into production by mistake. Whenever an exception was thrown it would pop-up a message box containing the error; normally they were just written to the log. It was a component that runs on a server. An unattended server...
Panic, Chaos, Destruction. My work here is done. Drink. Get drunk. Fall over - P O'H OK, I will win to day or my name isn't Ethel Crudacre! - DD Ethel Crudacre I cannot live by bread alone. Bacon and ketchup are needed as well. - Trollslayer Have a bit more patience with newbies. Of course some of them act dumb - they're often *students*, for heaven's sake - Terry Pratchett
Nagy Vilmos wrote:
An unattended server...
At least it was unattended... Last year I shipped a faceless utility that links a client's in-house till systems to the database of their online booking system. The till software was a train wreck written in PASCAL (still is in fact!), but thankfully I only had to poll for CSV files in a specified location, bump the data into the cloud, archive the original then delete it. I'm a Mac based web dev and was struggling with the client side stuff on Windoze. I thought I'd covered all the bases, and one clause that should never occur (according to the till software "guide" and my extensive "research") got the exasperated developer treatment. Needless to say, it happened, resulting in a modal dialogue popping up on the hotel chain's main computer in the accounts office: "This S**T should never happen! Damn you GOOGLE!" - That was one interesting phone call... :omg: Danny
-
I once programmed a function and added some assertions. For one of those assertions I figured it was impossible to break, or if it were, it must be someone meddling with that code. I considered removing the assertion entirely, but instead added a message box saying: "You shouldn't be seeing this error message. If you do, please speak to <my name>" When we sent a prototype to the client for testing a few weeks later, I promptly got a call, asking about that exact error message! Seems one of my colleagues was messing with my code after all. Only we didn't catch it in testing ourselves... On the plus side, that prototype was meant for testing and weeding out ... if not these kind of stupid messages, at least the cause for it (which was a real bug). Also the tester found it rather entertaining. :)
Stefan_Lang wrote:
On the plus side, that prototype was meant for testing and weeding out ... if not these kind of stupid messages, at least the cause for it (which was a real bug).
Same here, the software I was writing was to test the update to an existing board that had undergone a re-spin, code update & swapping to USB from D-type. I think at least some humour is required in this job or you go insane!
-
In a rush to email some code last night, I sent the wrong executable one which contained the following bit of test code
if (txtSerialNumberRead != txtSerialNumber_ReadIn)
{
MessageBox.Show("ERROR!! Kill all humans");
MessageBox.Show("Serial Number Entered Does Not Match **** Attached", "**** Tester", MessageBoxButtons.OK, MessageBoxIcon.Error);
}
//elseThe proper build does not offer death to humanity just the lower message, here's hoping the recipients look at there next mail before running it! Anybody else had this happen, shipped something with a dumb comment not hidden? or is it just me! Glenn
Some "too soon" releases are about code, and some are about test data.
Back in the late Seventies, when I worked, briefly, for a company that sold business management software (never again, please, Lord!), I was made responsible for an inventory control subsystem based upon a primitive proprietary database. As you can imagine, you can't test something like that without creating a substantial number of test records, which I did, tapping my, ah, fertile imagination for item types, names, and descriptions.
The testing went on for quite a long time, owing to the complex interaction of inventory and order processing. At the conclusion thereof, the customer, a Manhattan fashion designer, was jumping up and down in his insistence that the system be delivered at once. We were so desperate to get the **BLEEP!**ing thing out of our shop and into his hands that we forgot to purge the test records from the database.
The customer never bothered to check whether there was anything in the database. He simply had his data-entry people populate it with his long list of items for sale. My test records remained in the mix, undetected until the system was used to generate a printed catalog -- just lines of text on paper; this was the Seventies, after all -- to be sent to the company's redistributors.
You can imagine the consternation that ensued when one of the redistributors tried to order 1000 sets of the "sleepwear spurs," women's size 8, in burnished pewter. And that was one of the milder items I'd concocted.
(I am so much happier doing embedded real-time stuff!)
(This message is programming you in ways you cannot detect. Be afraid.)
-
Some "too soon" releases are about code, and some are about test data.
Back in the late Seventies, when I worked, briefly, for a company that sold business management software (never again, please, Lord!), I was made responsible for an inventory control subsystem based upon a primitive proprietary database. As you can imagine, you can't test something like that without creating a substantial number of test records, which I did, tapping my, ah, fertile imagination for item types, names, and descriptions.
The testing went on for quite a long time, owing to the complex interaction of inventory and order processing. At the conclusion thereof, the customer, a Manhattan fashion designer, was jumping up and down in his insistence that the system be delivered at once. We were so desperate to get the **BLEEP!**ing thing out of our shop and into his hands that we forgot to purge the test records from the database.
The customer never bothered to check whether there was anything in the database. He simply had his data-entry people populate it with his long list of items for sale. My test records remained in the mix, undetected until the system was used to generate a printed catalog -- just lines of text on paper; this was the Seventies, after all -- to be sent to the company's redistributors.
You can imagine the consternation that ensued when one of the redistributors tried to order 1000 sets of the "sleepwear spurs," women's size 8, in burnished pewter. And that was one of the milder items I'd concocted.
(I am so much happier doing embedded real-time stuff!)
(This message is programming you in ways you cannot detect. Be afraid.)
I know what you mean, when it goes off on a tangent it so much easier to see and can usually be solved with a soldering iron, I only started doing Windows stuff as at a previous company I walked in on the 'Whos gonna do it' conversation to be met with 'ohh, Glenn can'. Lesson learnt look busy at all times!
