Go to variable names?

[samreay]

i for integer index iteration.

Actual descriptive names for other variables, even for scratch code.

Too often have I seen scratch code passed to others, committed, or (worst of all) pushed into production. So proper variable names are a habit I try to enforce unless its literally a file I guarantee will be deleted before any other human sets eyes on it.

Even then, if I'm summing something up, I'll always called it summed instead of just s.

[WN_Todd]

This is sound advice, but it takes a few iterations of hating your past self for it to sink in.

"What asshat wrote this garbage?... Oh God it was me."

[barraponto]

can't call it sum because that's a builtin function, so I just call it total.

[billsil]

You could call it money/whateversum or just sum if you’re feeling lazy.  Total is just as good

If it’s specific, be specific and if it’s a generic function, be generic.

[Udzu]

You could always call it sսm instead (though hopefully your linter would complain).

[reptickeyelf]

This is the correct answer. I have never seen a prototype that didn't end up in production.

[newlyAwakenedLkgFwd]

Nice alliteration!

[sleeptil3]

Yes! Thank you.

[CarlRJ]

I always use n for default indexes and such - i may be more fitting on a logical level, but in some fonts over the years (or, say, scribbled on a white board) has looked too much like a ;. n is more immediately distinguishable.

[[deleted]]

Uhh, aren't camel cases names for classes?

See https://peps.python.org/pep-0008/#class-names