RLIOTD
-
Ridiculously long identifier of the day:
Connect_catcher_line_to_PIC_ink_port__Connect_duct_line_to_PIC_storage_port__Then_Step_UpAll 90 characters of it. Yes, I created it deliberately and yes I know it includes two occurrences of two underscores in a row. To make matters worse, it's anenumvalue, identifying a bit in a mask. Thank [diety-of-choice] for IntelliSense.Software Zen:
delete this;How about a GUID instead?! :rolleyes: :laugh:
A new .NET Serializer All in one Menu-Ribbon Bar Taking over the world since 1371!
-
Ridiculously long identifier of the day:
Connect_catcher_line_to_PIC_ink_port__Connect_duct_line_to_PIC_storage_port__Then_Step_UpAll 90 characters of it. Yes, I created it deliberately and yes I know it includes two occurrences of two underscores in a row. To make matters worse, it's anenumvalue, identifying a bit in a mask. Thank [diety-of-choice] for IntelliSense.Software Zen:
delete this; -
Ridiculously long identifier of the day:
Connect_catcher_line_to_PIC_ink_port__Connect_duct_line_to_PIC_storage_port__Then_Step_UpAll 90 characters of it. Yes, I created it deliberately and yes I know it includes two occurrences of two underscores in a row. To make matters worse, it's anenumvalue, identifying a bit in a mask. Thank [diety-of-choice] for IntelliSense.Software Zen:
delete this;When I started Uni, we were told we had to have meaningful identifiers. This was back in the punched card days (80 cols per card). So, as a silent protest, I wrote my Assessed Practical Work with every identifier being exactly 80 chars long. This mean that each identifier took a whole punched card and made the program unintelligible as it was impossible to use indentation. (It had one good benefit - I could just duplicate the cards with identifiers and slot them into the source deck as required, so I only had to type them once). I passed the Assessed Practical Work as the program worked and it had meaningful identifiers, but they were not amused. P.S. Language was Algol60 - one of the few languages that allowed spaces in identifiers - that helped make them meaningful but the code even less straight forward to read.
-
Ridiculously long identifier of the day:
Connect_catcher_line_to_PIC_ink_port__Connect_duct_line_to_PIC_storage_port__Then_Step_UpAll 90 characters of it. Yes, I created it deliberately and yes I know it includes two occurrences of two underscores in a row. To make matters worse, it's anenumvalue, identifying a bit in a mask. Thank [diety-of-choice] for IntelliSense.Software Zen:
delete this;What's "PIC"? Surely some acronym - and I do not understand it. Please write it out!
Oh sanctissimi Wilhelmus, Theodorus, et Fredericus!
-
What's "PIC"? Surely some acronym - and I do not understand it. Please write it out!
Oh sanctissimi Wilhelmus, Theodorus, et Fredericus!
By gosh, you're right! Sadly it's such a part of our vocabulary (pronounced, er, "pick"), I don't even remember what it's an acronym of. If I had to guess, it would be "Printhead Interface Controller", which would then make the proper identifier
Connect_catcher_line_to_PrintheadInterfaceController_ink_port__Connect_duct_line_to_PrintheadInterfaceController_storage_port__Then_Step_Up
I deliberately didn't replace the spaces in "Printhead Interface Controller" with underscores in order to emphasize that "PrintheadInterfaceController" is a component name.
Software Zen:
delete this; -
By gosh, you're right! Sadly it's such a part of our vocabulary (pronounced, er, "pick"), I don't even remember what it's an acronym of. If I had to guess, it would be "Printhead Interface Controller", which would then make the proper identifier
Connect_catcher_line_to_PrintheadInterfaceController_ink_port__Connect_duct_line_to_PrintheadInterfaceController_storage_port__Then_Step_Up
I deliberately didn't replace the spaces in "Printhead Interface Controller" with underscores in order to emphasize that "PrintheadInterfaceController" is a component name.
Software Zen:
delete this;Or Programmable Integrated Circuit? What does PIC stand for?[^] agrees, but also has Programmable Interrupt Controller and Peripheral Interface Controller and dozens of non-IT meanings. Take your pic(k). “When I use a word,’ Humpty Dumpty said in rather a scornful tone, ‘it means just what I choose it to mean — neither more nor less.’ ’The question is,’ said Alice, ‘whether you can make words mean so many different things.’ ’The question is,’ said Humpty Dumpty, ‘which is to be master — that’s all.” ― Lewis Carroll, Through the Looking Glass
-
Or Programmable Integrated Circuit? What does PIC stand for?[^] agrees, but also has Programmable Interrupt Controller and Peripheral Interface Controller and dozens of non-IT meanings. Take your pic(k). “When I use a word,’ Humpty Dumpty said in rather a scornful tone, ‘it means just what I choose it to mean — neither more nor less.’ ’The question is,’ said Alice, ‘whether you can make words mean so many different things.’ ’The question is,’ said Humpty Dumpty, ‘which is to be master — that’s all.” ― Lewis Carroll, Through the Looking Glass
In this case it's actually a board within our commercial ink-jet printer products. It accepts print data via a fiber optic connection and parcels it out to one or more arrays of jets. Depending upon configuration, we print somewhere around 1 billion (109) drops of ink per second, where each drop is around 6-9 picoliters. Our marketing created an interesting visual a while back. If each of our drops of ink were the size of a drop of rain, we dump an Olympic swimming pool every second.
Software Zen:
delete this; -
In this case it's actually a board within our commercial ink-jet printer products. It accepts print data via a fiber optic connection and parcels it out to one or more arrays of jets. Depending upon configuration, we print somewhere around 1 billion (109) drops of ink per second, where each drop is around 6-9 picoliters. Our marketing created an interesting visual a while back. If each of our drops of ink were the size of a drop of rain, we dump an Olympic swimming pool every second.
Software Zen:
delete this;Can the ink jets be directed so the user gets sprayed in the face? :laugh:
Robust Services Core | Software Techniques for Lemmings | Articles
The fox knows many things, but the hedgehog knows one big thing. -
Can the ink jets be directed so the user gets sprayed in the face? :laugh:
Robust Services Core | Software Techniques for Lemmings | Articles
The fox knows many things, but the hedgehog knows one big thing.Well, no. Ink-jet can get messy, however. Most of the bathrooms include a dispenser for a product called "Dye Gone" to get ink off your hands. A well-known incident occurred some years ago when an upper-level executive was being given the grand tour of some of our labs. A piece of tubing cut loose and sprayed the guy with a head-to-feet stream of yellow ink. We bought him a new suit.
Software Zen:
delete this; -
In this case it's actually a board within our commercial ink-jet printer products. It accepts print data via a fiber optic connection and parcels it out to one or more arrays of jets. Depending upon configuration, we print somewhere around 1 billion (109) drops of ink per second, where each drop is around 6-9 picoliters. Our marketing created an interesting visual a while back. If each of our drops of ink were the size of a drop of rain, we dump an Olympic swimming pool every second.
Software Zen:
delete this; -
When I started Uni, we were told we had to have meaningful identifiers. This was back in the punched card days (80 cols per card). So, as a silent protest, I wrote my Assessed Practical Work with every identifier being exactly 80 chars long. This mean that each identifier took a whole punched card and made the program unintelligible as it was impossible to use indentation. (It had one good benefit - I could just duplicate the cards with identifiers and slot them into the source deck as required, so I only had to type them once). I passed the Assessed Practical Work as the program worked and it had meaningful identifiers, but they were not amused. P.S. Language was Algol60 - one of the few languages that allowed spaces in identifiers - that helped make them meaningful but the code even less straight forward to read.
At these days, we were working in PL1, which allowed free format, like C, with columns 9-72 of every card filled with a code. One programmer from our team liked to fill all this area with a code. Probably to save punched cards. To fix a bug, he needed to retype everything from the buggy card to the end. He didn't like a bugs in the beginning.
