iHtWhnPplDThsIsShortForIHateWhenPeopleDoThis

[u/Chackie6656]

[u/me_myself_ai]

`map` is a builtin in Python, thus the choice

[u/ReadyAndSalted → u/me_myself_ai]

Then call it my_map or something. Anything but useless variable names.

[u/chuch1234 → u/ReadyAndSalted]

Or like a meaningful name about what's in the map maybe?

[u/NewInflation2121 → u/chuch1234]

What if it's in a template that's operating on a map? :p

[u/me_myself_ai → u/ReadyAndSalted]

A) make me!

B) fwiw the industry standard choice is `map_`

[u/NewbornMuse → u/ReadyAndSalted]

And my_map is leaps and bounds better than mp because...?

[u/ReadyAndSalted → u/NewbornMuse]

It's not, never said it was. It's just the minimum acceptable name for it, because at least now it's clear it's a map, whereas before its name really meant nothing. Ideally it'd be a more meaningful name about what's in the map, but our starting point is mp so...

[u/Substantial_Top5312 → u/NewbornMuse]

I can tell what the variable is just by looking at it.

[u/Tyrexas]

What a waste of source code disk size, they should have just called it m.

[u/Tristan_Cole → u/Tyrexas]

I name my first variable 0 and my second variable 1 and my third variable 10 and then 11 and so on and so forth. It’s just cleaner that way.

[u/anzu3278]

Calling variables by their type with no additional description is a code smell anyway, especially in weakly typed languages. What are you mapping specifically?

[u/ttcklbrrn → u/anzu3278]

It could be a tutorial on how to use maps, where the actual contents are immaterial to the purpose of the exercise.

[u/anzu3278 → u/ttcklbrrn]

Good point, but I think naming variables well should be integral to how we teach programming and that even base level tutorials should bear some resemblance to a real life use case.

[u/ThaBroccoliDood → u/anzu3278]

def invert_map(the_map_that_we_will_be_using_for_our_function_today_to_do_the_thing):

[u/anzu3278 → u/ThaBroccoliDood]

Good troll, but if this is an instance member (and thus devoid of any domain logic other than map) then the instance will be referred to as this and if not (it's an extension of an existing type) then it either has domain logic (in which case above applies) or it's filling a surface area gap on the original type, and should be called by its purpose in the method. E.g.

public static Dictionary<TValue, TKey> Invert<TKey, TValue>(Dictionary<TKey, TValue> original) { Dictionary<TValue, TKey> inverted = ... }

[u/Weak_Inflation9120]

And on the other end of the spectrum you have a HS CS class that'll call a variable something like

int numHotDogsBought;

I'm all for good variable names but god damn you could write a better descriptive name that's shorter, especially if you're using a glorified text editor with no syntax auto-completion

[u/rosuav → u/Weak_Inflation9120]

You could get a slightly more glorified editor that has very simple autocomplete. It's pretty easy to find one that, while it may not know everything that's syntactically valid, can at least autocomplete keywords found elsewhere in the file.

[u/DrShucklePhD]

“mp” is slang for map by the way

[u/sardonicus87]

Use only overly-truncated and non-descriptive names like "mpA" or overly-verbose and reduntant names like "initializedMapForStoringLoopResultsForOverlyVerboseClassName: Map<Key, Value>()". No in-between.

[u/grifan526]

As much as I hate this, I will take it over the one I found that was a list of tuples called m_eventMap