I have done a stupid!!!!!
-
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 have really enjoyed this lounge topic...
You have triggered a lot of great responses and memories.
I am sure that there are heaps more out there.I never put profanities in letters or code without using an X or XXX.
I scan for these prior to finalising and saving over them.
In fact I stopped using the profanities at all due to the risk and now replace these with the X or XXX.
I will often give weird or profound names to functions and modules. This humours me.The X or XXX means revisit this.
However in one of my offers the client returned with "Wow we accept your offer and we can not believe that you will do all this work for $X. $10 seems very cheap for this amount of work." I retracted my offer on the grounds that I do not quote in roman dollars and resubmitted with the $X replaced with real data.
I always hide some cryptic stuff in all of my applications, and whilst these may be stupid, they are in fact deliberate and planned. I love these hidden bits of stupid harmless bits of code that usually are a dedication to someone special or just a silly response to user input.
The most stupid thing that I released was embarrassing and stupid. Years ago I decided to learn Pascal. That wasn't a stupid thing, except that I never did any Pascal dev as I ventured into C++ after this distraction. It was Turbo Pascal and I just liked the turbo bit. I was interested in the single bit speaker sound output and wrote a beginners "Virus Found" with dumb text app with mad sound effects. We had a DOS security application that used to use function keys to shell to other apps. We used this for promotions and for testing. During one of our promotions we used the system to award door prizes to participants. They would read their data keys and the system would respond with a random response re the prize.
Our senior Techo did some upgrades to the latest version and used the test / promo box to generate these installs. The result was that a major law enforcement agency called me saying that they had a virus on their security system and angrily said please explain, and I could hear the sound effects in the background of the telephone call. Next an international oriented goverment agency called to say that they had a virus as every time they left their front door open the system raised a popup alarm saying "Congratulations you have won a bottle of wine".
All that was about 20 years ago.
All the embarrassing things since then have been planned and deliberate.
-
I have really enjoyed this lounge topic...
You have triggered a lot of great responses and memories.
I am sure that there are heaps more out there.I never put profanities in letters or code without using an X or XXX.
I scan for these prior to finalising and saving over them.
In fact I stopped using the profanities at all due to the risk and now replace these with the X or XXX.
I will often give weird or profound names to functions and modules. This humours me.The X or XXX means revisit this.
However in one of my offers the client returned with "Wow we accept your offer and we can not believe that you will do all this work for $X. $10 seems very cheap for this amount of work." I retracted my offer on the grounds that I do not quote in roman dollars and resubmitted with the $X replaced with real data.
I always hide some cryptic stuff in all of my applications, and whilst these may be stupid, they are in fact deliberate and planned. I love these hidden bits of stupid harmless bits of code that usually are a dedication to someone special or just a silly response to user input.
The most stupid thing that I released was embarrassing and stupid. Years ago I decided to learn Pascal. That wasn't a stupid thing, except that I never did any Pascal dev as I ventured into C++ after this distraction. It was Turbo Pascal and I just liked the turbo bit. I was interested in the single bit speaker sound output and wrote a beginners "Virus Found" with dumb text app with mad sound effects. We had a DOS security application that used to use function keys to shell to other apps. We used this for promotions and for testing. During one of our promotions we used the system to award door prizes to participants. They would read their data keys and the system would respond with a random response re the prize.
Our senior Techo did some upgrades to the latest version and used the test / promo box to generate these installs. The result was that a major law enforcement agency called me saying that they had a virus on their security system and angrily said please explain, and I could hear the sound effects in the background of the telephone call. Next an international oriented goverment agency called to say that they had a virus as every time they left their front door open the system raised a popup alarm saying "Congratulations you have won a bottle of wine".
All that was about 20 years ago.
All the embarrassing things since then have been planned and deliberate.
Well the main thing I got from this was I'm not alone. I was expecting a set of snobby I have never done that, the most reassuring thing was there were none (and also my opposite number got to the mail server before it got down loaded, I now owe him a case of Beer,<> he has to get back to me with the brand <>. As for profanities never have in work code private/learning code different matter, Monty Python & standard geeky quotes, X-Files, Lemmings, one instance "The Truth is Out There, but not in here!" springs immediately to mind and "Oh No!, Kabang!" when a buffer broke and resulting data flood crashed the PC. I am more of a Hardware guy than a Softie and thought it was my lack of deployment experience that led to it happening
-
Why, oh Why can't there be a means of getting back an email once it you look at it, even the post office give you the option of using a wire coat hanger. (No I was not interfering with Her Majesty's Postal Service, I assure you Officer) :)
-
Precisely why I have the "undo" button on my gmail account and a delay on my work Outlook for sending.
Thats a good idea! hadn't though of that ;)
-
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
quick one when I was very young... had a dataease database, that I was using to mailshot clients with, part of the data export procedure to create the mailshot was it would give them a client code based on the first 3 letters of the first name of the company followed by the first letter of any other word (I was very young and green) took a while before anyone noticed what it was calling "Cunningham Turner Solicitors"...
-
quick one when I was very young... had a dataease database, that I was using to mailshot clients with, part of the data export procedure to create the mailshot was it would give them a client code based on the first 3 letters of the first name of the company followed by the first letter of any other word (I was very young and green) took a while before anyone noticed what it was calling "Cunningham Turner Solicitors"...
Like it!
-
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 used to work for a firm that made tracking electronics and a colleague of mine was was testing a touch memory reader. For those that don't know, Dallas touch memory devices primarily contain (among other things) a "semi-unique" serial number that you can use for identification purposes which can be read by electrical contact using a two-wire protocol. The thing was like a gun with a trigger and a small LCD display. The idea was you touch the memory device, read its serial number it reports what it was purporting to represent on the LCD. Well, being the wag that he was, the test data loaded into the prototype unit were such edifying gems as "Betty Swollocks" and "Mary Hinge". This was great fun until a customer came around for a demo and was not very impressed by what she saw.... Yep, the moral of the story is just don't do it. :D
-
I am regarded the same way, give it Glenn, if he can't break it no one can with ease!
Nothing quite as embarassing as that. I occasionally would put a movie quote in the comments as a joke for the other developers, in case we had to work on each other's code. So, in this one Excel macro, which was summing up values, I wrote: "There is not enough time to explain, let me sum up..." - Inigo Montoya A year or so went by, then I got a phone call from someone who had run the macro, and received an error and had chosen "Debug", which of course displayed the line which the error had occurred and the comment above.
-
Thats a good idea! hadn't though of that ;)
-
quick one when I was very young... had a dataease database, that I was using to mailshot clients with, part of the data export procedure to create the mailshot was it would give them a client code based on the first 3 letters of the first name of the company followed by the first letter of any other word (I was very young and green) took a while before anyone noticed what it was calling "Cunningham Turner Solicitors"...
-
I used to work for a firm that made tracking electronics and a colleague of mine was was testing a touch memory reader. For those that don't know, Dallas touch memory devices primarily contain (among other things) a "semi-unique" serial number that you can use for identification purposes which can be read by electrical contact using a two-wire protocol. The thing was like a gun with a trigger and a small LCD display. The idea was you touch the memory device, read its serial number it reports what it was purporting to represent on the LCD. Well, being the wag that he was, the test data loaded into the prototype unit were such edifying gems as "Betty Swollocks" and "Mary Hinge". This was great fun until a customer came around for a demo and was not very impressed by what she saw.... Yep, the moral of the story is just don't do it. :D
but if you must try not to be too offensive a little clean humour can at times be useful.
-
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
That isn't as far off of normal error messages as you think. Consider what non-computer people think when they encounter error messages that make sense to us. For instance, my grandfather a few years ago told me the story of getting his first computer, using it for a while, and then suddenly a screen came up that said, "Illegal instruction. Fatal error." and he nervously glanced out the window to see if any police cars were around, and wondered if his will should be in order. He was joking when he told the story, but he probably didn't have any idea what that message actually meant, whereas it had never even occurred to me that those words would mean something completely different to a non-programmer.
-
That isn't as far off of normal error messages as you think. Consider what non-computer people think when they encounter error messages that make sense to us. For instance, my grandfather a few years ago told me the story of getting his first computer, using it for a while, and then suddenly a screen came up that said, "Illegal instruction. Fatal error." and he nervously glanced out the window to see if any police cars were around, and wondered if his will should be in order. He was joking when he told the story, but he probably didn't have any idea what that message actually meant, whereas it had never even occurred to me that those words would mean something completely different to a non-programmer.
I was afraid when I posted this that "proper" Softies would be very unsympathetic and scornful of some Hardware guy scratching at Windows, I have in the past when I was working on some embedded code and needed a way of showing an error made an LED flash SOS in Morse code (really just messing around until some body got back to me). That is now a valued feature of that product as it gives service guys an indication of what has gone wrong.
-
but if you must try not to be too offensive a little clean humour can at times be useful.
Yeah, it certainly does help to inject a little humour into your work just to humanise it a little, I'm all for that. If you do, you just have to be careful who sees it :D On a related topic, at the same place, albeit in a different department and some years prior, I did see a serial protocol used to communicate with a handheld. We had two types of a particular application that ran on this Symbol handheld machine and to differentiate, the writer added a 4-character "identifier" to the stream header. In this case, the word was "FUKU". No chance of a customer seeing that, but it did bring a smile to me face.
-
Yeah, it certainly does help to inject a little humour into your work just to humanise it a little, I'm all for that. If you do, you just have to be careful who sees it :D On a related topic, at the same place, albeit in a different department and some years prior, I did see a serial protocol used to communicate with a handheld. We had two types of a particular application that ran on this Symbol handheld machine and to differentiate, the writer added a 4-character "identifier" to the stream header. In this case, the word was "FUKU". No chance of a customer seeing that, but it did bring a smile to me face.
Ha, I knew it! also Symbol handheld, #FUKU# sounds familiar I might know the author in previous job.
-
Ha, I knew it! also Symbol handheld, #FUKU# sounds familiar I might know the author in previous job.
There's actually no harm in being specific here since the company has long since disappeared. The company was Zengrange in Leeds, England and it was for a long defunct system for BOC. The guy who wrote the program has a nick name which I can't remember although it might have started with "M". No names, no pack drill and all that... If you wish to carry the conversation further, feel free to pm me.
-
There's actually no harm in being specific here since the company has long since disappeared. The company was Zengrange in Leeds, England and it was for a long defunct system for BOC. The guy who wrote the program has a nick name which I can't remember although it might have started with "M". No names, no pack drill and all that... If you wish to carry the conversation further, feel free to pm me.
Oh not the guy I was think of. However the bit of code I was referring to came from the Leeds area so we might have inherited from Zengrange and modded it for an RF-ID use. Does the name 'Camper' ring any bells. Not too sure of how use the Private Messenger. Glenn
-
Oh not the guy I was think of. However the bit of code I was referring to came from the Leeds area so we might have inherited from Zengrange and modded it for an RF-ID use. Does the name 'Camper' ring any bells. Not too sure of how use the Private Messenger. Glenn
No worries. I seem to remember that the software was for BOC/ICI to do with their tracking of dewar deliveries of gases I believe. I didn't work much on the code itself although I did do some mods on it. If memory serves me correctly, we used some of the REALLY early Symbol handhelds that you programmed by dropping in an EPROM. Testing was a bit of a trial. We had to compile everything up, download to a burner, erase and program up a prom, stick it in and try it. Ah, happy days. At some point I think we did try RFID tags, the idea being that the gas bottles etc would be tagged and you could scan the entire delivery by just being in close proximity. But reception was pretty bad and the metal of the containers would hide some of the tags so reliability was a problem. Mostly barcodes were used instead although they would get scuffed and rubbed off. The two guys that were mainly involved were Neil Carman and the other guy whose name escapes me for the moment although I do remember that he had a nickname (something like "murph") and was a really keen rally car racer. 'Twas all a really long time ago.
-
No worries. I seem to remember that the software was for BOC/ICI to do with their tracking of dewar deliveries of gases I believe. I didn't work much on the code itself although I did do some mods on it. If memory serves me correctly, we used some of the REALLY early Symbol handhelds that you programmed by dropping in an EPROM. Testing was a bit of a trial. We had to compile everything up, download to a burner, erase and program up a prom, stick it in and try it. Ah, happy days. At some point I think we did try RFID tags, the idea being that the gas bottles etc would be tagged and you could scan the entire delivery by just being in close proximity. But reception was pretty bad and the metal of the containers would hide some of the tags so reliability was a problem. Mostly barcodes were used instead although they would get scuffed and rubbed off. The two guys that were mainly involved were Neil Carman and the other guy whose name escapes me for the moment although I do remember that he had a nickname (something like "murph") and was a really keen rally car racer. 'Twas all a really long time ago.
I think I have met (or crossed swords with more accurately) Neil Carman (or was Caraman?), to do with 13.56 Tag reflections off an antenna I designed. (cue dream sequence wibbly wobbly lines) Murph sounds familiar. Small, Small world! Glenn