Bad spelling in code.

BobsLawnService

Expert Member
Joined
Jun 18, 2010
Messages
2,924
Reaction score
13
I have recently started work on a project coded by a lead developer who didn't much bother with spelling.

About 20% of the variable names and methods are badly misspelled.

I make the occasional spelling error but every time I work on the code I end up feeling like someone is sticking needles in my eyes - not to mention the time wasted debugging JavaScript.

Guys, please. Let's have a little more OCD.
 
Irks me too :/

Not so much on general programs, but simulations and maths ones where function names are important....

My functions are my functions. Let me parse your functions if I need them but dont make me look inside.
 
I've noticed that there is a direct correlation between the number of spelling mistakes and the quality of the code itself.
 
I've noticed that there is a direct correlation between the number of spelling mistakes and the quality of the code itself.

Can't say I've ever noticed this. I've worked on some code bases with horrific spelling, but code ran 100%.
 
Can't say I've ever noticed this. I've worked on some code bases with horrific spelling, but code ran 100%.

Bad spelling isn't a problem in code as long as the bad spelling is consistant.
 
I have recently started work on a project coded by a lead developer who didn't much bother with spelling.

About 20% of the variable names and methods are badly misspelled.

I make the occasional spelling error but every time I work on the code I end up feeling like someone is sticking needles in my eyes - not to mention the time wasted debugging JavaScript.

Guys, please. Let's have a little more OCD.

misspelled is a word I often misspell. True story.


But on topic, a global search/replace across the code - would that help or does it run the risk of creating conflicts?
 
misspelled is a word I often misspell. True story.


But on topic, a global search/replace across the code - would that help or does it run the risk of creating conflicts?

I'm new here and the impression I get is that you don't refactor code.

It's one of those "Maybe I've made a mistake moves." The guy reviewing my code wouldn't pass one of my code reviews.

I think I'm just getting old and cranky.
 
Spelling doesnt bother me much, but when developers define variable names as #A-A, #A-B , #A-AB it really gets me going on a rant.
 
Spelling doesnt bother me much, but when developers define variable names as #A-A, #A-B , #A-AB it really gets me going on a rant.

You would love some of my calculation routines ;)
 
Assuming you got handed a project - with lots of misspellings etc.

Can you create aliases for the misspellings, or do you either work with the misspellings? Or do you do a global search and replace and hope for the best?
 
Assuming you got handed a project - with lots of misspellings etc.

Can you create aliases for the misspellings, or do you either work with the misspellings? Or do you do a global search and replace and hope for the best?

I usually just fix the spelling mistakes, you break one function you tend to see where it all collapses. Making aliases would be a very bad move lol.
 
Assuming you got handed a project - with lots of misspellings etc.

Can you create aliases for the misspellings, or do you either work with the misspellings? Or do you do a global search and replace and hope for the best?

Redefine all the variables with the correct spelling. :D
 
We have a few mistakes ... often by Afrikaans developers getting the wording wrong for an English word e.g. Intergration.
 
Worst is when they misspell field names in a table. Not so quick to fix then.

I find it even more painful when a deliver brings in their **** naming convention.
 
Is this face**** where you +1 everything?

Nope.

That would be Google+.

In any case, my apologies for striking a nerve. I was merely agreeing with your point. There's nothing worse than inconsistency in code. It means that the developer (assuming he/she is conversing in the same language as you) doesn't think that the priority of readability or elegance belongs high on their list.

Code should be written first and foremost for Humans, not machines. If the code works, the compiler doesn't give a damn, but I will. Because it means have to spend more time trying to understand what the function does. The code with bad spelling is written once but read more.
 
Top
Sign up to the MyBroadband newsletter
X