Even for indexes I do index or something more specific for what it’s indexing. Any simple iteration I just do map or each so the only time I ever need to actually index things is for more complex scenarios in which case it’s worth it to have better names. Also with modem IDEs, auto complete is really good so you don’t need to write a full variable name more than once.
that’s good too. I recommended k over j if using single letters, but I actually tend to use idx when using indices, and more descriptive idx_this, idx_that for rare index-based nested loops.
When I was a baby coder back in the 90s we were taught that these names were meant to save space in the symbol table because at one time space was so limited that naming your variable n rather than numElementsInArray would have an impact
 [@programmerhumor](https://lemmy.ml/c/programmerhumor) [email protected]](https://files.mastodon.social/media_attachments/files/110/957/578/506/504/291/original/37350059e5bb4a36.png){kind=link}
Unless they’re indices, do yourself a favor and use meaningful names instead.
I avoid index iterations the most I can tbh. And for nested loops,
iandkis more readable.Even for indexes I do
indexor something more specific for what it’s indexing. Any simple iteration I just domaporeachso the only time I ever need to actually index things is for more complex scenarios in which case it’s worth it to have better names. Also with modem IDEs, auto complete is really good so you don’t need to write a full variable name more than once.that’s good too. I recommended
koverjif using single letters, but I actually tend to useidxwhen using indices, and more descriptiveidx_this,idx_thatfor rare index-based nested loops.When I was a baby coder back in the 90s we were taught that these names were meant to save space in the symbol table because at one time space was so limited that naming your variable n rather than numElementsInArray would have an impact
This is the way.
Even then,
for (int index = 0; index < 10; index++)all the way.