SMS-speak in code (aka 'It had to happen')
-
I decided to rewrite a colleague's code, since it was a steaming pile of dung. X| Imagine my horror when I found variables like FndsMovd, to denote the funds moved. He was too lazy to type an extra u and e? :wtf: Intc was intercept, Errs was Errors and regSusp was regional suspense. WTF? How on earth is somebody who's looking at the code for the first time to know what they mean? 4 years of experience. :sigh: If I ever find such people working for me... :mad: I suspect if confronted, he would say he used shorter variable names for efficiency. :suss: ~ Nazgûl
-
I decided to rewrite a colleague's code, since it was a steaming pile of dung. X| Imagine my horror when I found variables like FndsMovd, to denote the funds moved. He was too lazy to type an extra u and e? :wtf: Intc was intercept, Errs was Errors and regSusp was regional suspense. WTF? How on earth is somebody who's looking at the code for the first time to know what they mean? 4 years of experience. :sigh: If I ever find such people working for me... :mad: I suspect if confronted, he would say he used shorter variable names for efficiency. :suss: ~ Nazgûl
You youngsters :rolleyes:. Back when I first learned programming (in FORTRAN), we had six whole characters for variable names. A name like "
OMIDBK" would be short for "OutputManagerInitializeDataBaseKey".My other CP account wrote:
How on earth is somebody who's looking at the code for the first time to know what they mean?
// try some of these
:laugh:
Software Zen:
delete this; -
I decided to rewrite a colleague's code, since it was a steaming pile of dung. X| Imagine my horror when I found variables like FndsMovd, to denote the funds moved. He was too lazy to type an extra u and e? :wtf: Intc was intercept, Errs was Errors and regSusp was regional suspense. WTF? How on earth is somebody who's looking at the code for the first time to know what they mean? 4 years of experience. :sigh: If I ever find such people working for me... :mad: I suspect if confronted, he would say he used shorter variable names for efficiency. :suss: ~ Nazgûl
Well, certainly nice variable name help for clarity. But going all the way to say that code quality is in direct relation to variable name is a bit far fetched, don't you think? :-D
-
Well, certainly nice variable name help for clarity. But going all the way to say that code quality is in direct relation to variable name is a bit far fetched, don't you think? :-D
Super Lloyd wrote:
is a bit far fetched, don't you think?
I hope you are kidding.
We say "get a life" to each other, disappointed or jokingly. What we forget, though, is that this is possibly the most destructive advice you can give to a geek.
boost your code || Fold With Us! || sighist -
You youngsters :rolleyes:. Back when I first learned programming (in FORTRAN), we had six whole characters for variable names. A name like "
OMIDBK" would be short for "OutputManagerInitializeDataBaseKey".My other CP account wrote:
How on earth is somebody who's looking at the code for the first time to know what they mean?
// try some of these
:laugh:
Software Zen:
delete this; -
Well, certainly nice variable name help for clarity. But going all the way to say that code quality is in direct relation to variable name is a bit far fetched, don't you think? :-D
Super Lloyd wrote:
But going all the way to say that code quality is in direct relation to variable name is a bit far fetched, don't you think?
You're joking, right? :| I'm going to post other, better, shinier gems; but first, I need to complete cleaning up this mess. ~ Nazgûl +++++++++++++
-
Well, certainly nice variable name help for clarity. But going all the way to say that code quality is in direct relation to variable name is a bit far fetched, don't you think? :-D
Let's put it this way. Suppose Da Vinci had used a pushbroom to paint The Last Supper. Do you think the results would be the same?
Software Zen:
delete this; -
With such restrictions you often find clarity in a certain structure, such as the first two mean this, the next two that etc. The vowel-o-phobe is normally worse. I used to get high on life until I realized that life was cut with morons - Unknown
Unfortunately, I work with a guy like the vowel-o-phobe. The good thing is, he's consistent in how he does it, so at least you know what to expect. It could be the original complaint is partially based on inconsistency.
Software Zen:
delete this; -
Well, certainly nice variable name help for clarity. But going all the way to say that code quality is in direct relation to variable name is a bit far fetched, don't you think? :-D
Super Lloyd wrote:
But going all the way to say that code quality is in direct relation to variable name is a bit far fetched, don't you think?
IMO, yes. Cleek | Image Toolkits | Thumbnail maker
-
I decided to rewrite a colleague's code, since it was a steaming pile of dung. X| Imagine my horror when I found variables like FndsMovd, to denote the funds moved. He was too lazy to type an extra u and e? :wtf: Intc was intercept, Errs was Errors and regSusp was regional suspense. WTF? How on earth is somebody who's looking at the code for the first time to know what they mean? 4 years of experience. :sigh: If I ever find such people working for me... :mad: I suspect if confronted, he would say he used shorter variable names for efficiency. :suss: ~ Nazgûl
The others are horrible but Errs is perfectly acceptable IMO. regards, Paul Watson Ireland Colib and ilikecameras. K(arl) wrote: oh, and BTW, CHRISTIAN ISN'T A PARADOX, HE IS A TASMANIAN!
-
Well, certainly nice variable name help for clarity. But going all the way to say that code quality is in direct relation to variable name is a bit far fetched, don't you think? :-D
Code quality is measured in many more important ways than "it works". ------- sig starts "I've heard some drivers saying, 'We're going too fast here...'. If you're not here to race, go the hell home - don't come here and grumble about going too fast. Why don't you tie a kerosene rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt "...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
-
Code quality is measured in many more important ways than "it works". ------- sig starts "I've heard some drivers saying, 'We're going too fast here...'. If you're not here to race, go the hell home - don't come here and grumble about going too fast. Why don't you tie a kerosene rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt "...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
John Simmons / outlaw programmer wrote:
Code quality is measured in many more important ways than "it works".
So? . . . . . . . . Exemple: I worked with dyslexic, doesn't prevent them of being good coder with efficient and maintainable code. And I think the 2 above quality matter way more that variable naming.
-
I decided to rewrite a colleague's code, since it was a steaming pile of dung. X| Imagine my horror when I found variables like FndsMovd, to denote the funds moved. He was too lazy to type an extra u and e? :wtf: Intc was intercept, Errs was Errors and regSusp was regional suspense. WTF? How on earth is somebody who's looking at the code for the first time to know what they mean? 4 years of experience. :sigh: If I ever find such people working for me... :mad: I suspect if confronted, he would say he used shorter variable names for efficiency. :suss: ~ Nazgûl
Pfft... that's nothing. I get a whopping 8 characters to work with. Often there's no comment associated with the definition, so I have to dig through the code to figure out what HLDGFREM or ONEQ5 does. It's not unusual to find variables cut and pasted from other programs that aren't used at all, or find multiple versions of a constant like HEX0 and ZERO. It's a freaking joy. :sigh: BW
If you're not part of the solution, you're part of the precipitate.
-- Steven Wright -
John Simmons / outlaw programmer wrote:
Code quality is measured in many more important ways than "it works".
So? . . . . . . . . Exemple: I worked with dyslexic, doesn't prevent them of being good coder with efficient and maintainable code. And I think the 2 above quality matter way more that variable naming.
Super Lloyd wrote:
So?
Lloyd, there's much more. :| Think of what I posted today as the trailer. ;P ~ Nazgûl +++++++++++++
-
Well, certainly nice variable name help for clarity. But going all the way to say that code quality is in direct relation to variable name is a bit far fetched, don't you think? :-D
-
The others are horrible but Errs is perfectly acceptable IMO. regards, Paul Watson Ireland Colib and ilikecameras. K(arl) wrote: oh, and BTW, CHRISTIAN ISN'T A PARADOX, HE IS A TASMANIAN!
-
Err is a common abbreviation and Errs can be the plural of it. regards, Paul Watson Ireland Colib and ilikecameras. K(arl) wrote: oh, and BTW, CHRISTIAN ISN'T A PARADOX, HE IS A TASMANIAN!
-
I decided to rewrite a colleague's code, since it was a steaming pile of dung. X| Imagine my horror when I found variables like FndsMovd, to denote the funds moved. He was too lazy to type an extra u and e? :wtf: Intc was intercept, Errs was Errors and regSusp was regional suspense. WTF? How on earth is somebody who's looking at the code for the first time to know what they mean? 4 years of experience. :sigh: If I ever find such people working for me... :mad: I suspect if confronted, he would say he used shorter variable names for efficiency. :suss: ~ Nazgûl
Bah, thats nothing compared to the old system we have here ;-) called "Raindance" from swedish "vm-data" all classes are named: cl001-cl999 and all modules (a'la vb6 modules) are named pr001-pr999 and to make it even more painful , cl001 can exist in different "nodes" so there might be 3 cl001 in different places :-) how'bout that? ;) X|
-
John Simmons / outlaw programmer wrote:
Code quality is measured in many more important ways than "it works".
So? . . . . . . . . Exemple: I worked with dyslexic, doesn't prevent them of being good coder with efficient and maintainable code. And I think the 2 above quality matter way more that variable naming.
Super Lloyd wrote:
I worked with dyslexic, doesn't prevent them of being good coder with efficient and maintainable code.
So... what you're saying is... suffering from a neurologic disorder that makes it more difficult to interpret symbols, and the social disorder of being too damn lazy to type in vowels are essentially the same thing? Right. :|
---- Scripts i've known... CPhog 0.9.9 - make CP better. Forum Bookmark 0.2.1 - bookmark forum posts on Pensieve Print forum 0.1.2 - printer-friendly forums
-
I decided to rewrite a colleague's code, since it was a steaming pile of dung. X| Imagine my horror when I found variables like FndsMovd, to denote the funds moved. He was too lazy to type an extra u and e? :wtf: Intc was intercept, Errs was Errors and regSusp was regional suspense. WTF? How on earth is somebody who's looking at the code for the first time to know what they mean? 4 years of experience. :sigh: If I ever find such people working for me... :mad: I suspect if confronted, he would say he used shorter variable names for efficiency. :suss: ~ Nazgûl
Co-workers often get pissed off with me because I use extremely long and descriptive variable names. A quick sample from some code I'm working on now:
isStandardDisabledSyncActions_AutoDetectInternetConn eSearchIndexUpdatesWindowType gLocalPortListenerStartNewChannelWizardMsgIt's fine for me since I have a widescreen display and Visual Assist (motto: Intellisense that works) but it's a major PITA for people who don't ;P:laugh:
The two most common elements in the universe are Hydrogen and stupidity. - Harlan Ellison Awasu 2.2 [^]: A free RSS/Atom feed reader with support for Code Project.
