re: Cleaning Up Your Code: Good Names VIEW POST

VIEW FULL DISCUSSION

Also don't forget that in some cases it's perfectly valid to use 'short' names.

It's ok to use i for first iteration and then go to j , k etc for 'sub iterations' since it's a really common practice. Same for 2d/3d coordinates, x y z are perfectly valid, just remember to have it self contained in a decently named function.

I completely agree!

For trivial pieces of code like for loops or even a function that just prints out an array, variable names aren't so important.

Naming conventions become more and more important once you start writing code that can't be trivially understood.

I completely disagree. There is no trivial code. For loops especially need to have clear variable naming. Iterating over i, j, may be a common practice but it does not make it less awful. It has to absolutely clear what data is processed inside a method. Are you sure you even know what to expect if you can't name it?

Of course, for loops by definition point to an 'index' (hence the initial i), and that index is going to be called on a clear named variable.

Yes, "traditional" for-loops work that way... My opinion stems from mainly using languages that have an iterator-based for-loop where the "i" is not the index, but an item.

code of conduct - report abuse