A common problem (before learning it is impossible/fraught with danger) is categorisation, like sorting of strings.
Say you have a text, and need to count words of different lengths.
One intuitive approach is to pass through it once and add each word to a list for the corresponding length, as well as making lists as needed. No 7 letter words, no 7-letter-word-list, even though there are longer words.
As humans we're good at sorting things into an unknown number of categories, and we have to unlearn that for programming
I like the implication that programmers aren't humans, but a sort of alien being naturally apt at algorithmic thinking, while puny humans are an irrational species that needs to undergo training from the mighty race of programmers if they hope to get into the field brought us here by the aliens
'List' is the correct abstract term for any data structure that holds a given number of values in an order, regardless of the implementation. So Python's List, or C++'s Array or Vector, or a Linked List are all considered lists in the abstract sense.
This makes a ton of sense and I think you probably solved this mystery for me.
"Oh I need to iterate over something, and keep track of new information as I do it, therefore I should be able to create 'dynamic variables' as I progress."
I remember wondering this when I was first trying to self learn. It's because I needed a map (or list + struct or something) and was such a noob I didn't know what maps were. Whatever material I was learning from wasn't good enough, especially for winging things. Plus I was trying to learn C++ and maps aren't quite so built into the language as they are with a better first language like Python.
In lower level languages like C/C++ the reason becomes much more apparent when you learn about memory allocation and management (as a bonus it also really helps to understand how OS's handle memory). Dynamically declaring variables in a loop would mean you need to allocate a chunk of memory for each variable that's generated on the fly, most of, if not all of the dynamically declared variables would not even use most of their allocated memory resulting in a ton of extra overhead and wasted space within memory. An array is usually the answer when someone asks how to dynamically define variables. With an array you allocate the space needed in memory and can iterate across it block by block resulting in more control and efficiency within your reserved memory block. Linked lists are also a fun thing to look into when you aren't sure how big your array needs to be. It's a hard question to answer in a 100 level class because the answer actually goes pretty deep into low level programming, operating system and hardware principles.
I distinctly remember asking this question during a 100 level programming class but I just can not remember why I'd ever want to do this?
What problem could I have possibly have been trying to solve where this would seem like the answer.
A common problem (before learning it is impossible/fraught with danger) is categorisation, like sorting of strings.
Say you have a text, and need to count words of different lengths.
One intuitive approach is to pass through it once and add each word to a list for the corresponding length, as well as making lists as needed. No 7 letter words, no 7-letter-word-list, even though there are longer words.
As humans we're good at sorting things into an unknown number of categories, and we have to unlearn that for programming
Would one not just use a dict/hashmap with int keys labelling lengths and the list of strings as the values?
A programmer might, as trained/conditioned by the limits of programming languages.
A human would intuitively not, these are meaningless and/or convoluted concepts to the untrained human.
I like the implication that programmers aren't humans, but a sort of alien being naturally apt at algorithmic thinking, while puny humans are an irrational species that needs to undergo training from the mighty race of programmers if they hope to get into the field brought us here by the aliens
Found the Python guy.
'List' is the correct abstract term for any data structure that holds a given number of values in an order, regardless of the implementation. So Python's List, or C++'s Array or Vector, or a Linked List are all considered lists in the abstract sense.
I did use 'list' and forgot it is called an 'array' or 'vector' in other languages. So sure, close enough :-)
Because those are limited to Python? 😜
This makes a ton of sense and I think you probably solved this mystery for me.
"Oh I need to iterate over something, and keep track of new information as I do it, therefore I should be able to create 'dynamic variables' as I progress."
Yep, what you failed to realise at the time is you've just invented a dynamic data structure like a list or a dictionary.
I remember wondering this when I was first trying to self learn. It's because I needed a map (or list + struct or something) and was such a noob I didn't know what maps were. Whatever material I was learning from wasn't good enough, especially for winging things. Plus I was trying to learn C++ and maps aren't quite so built into the language as they are with a better first language like Python.
In lower level languages like C/C++ the reason becomes much more apparent when you learn about memory allocation and management (as a bonus it also really helps to understand how OS's handle memory). Dynamically declaring variables in a loop would mean you need to allocate a chunk of memory for each variable that's generated on the fly, most of, if not all of the dynamically declared variables would not even use most of their allocated memory resulting in a ton of extra overhead and wasted space within memory. An array is usually the answer when someone asks how to dynamically define variables. With an array you allocate the space needed in memory and can iterate across it block by block resulting in more control and efficiency within your reserved memory block. Linked lists are also a fun thing to look into when you aren't sure how big your array needs to be. It's a hard question to answer in a 100 level class because the answer actually goes pretty deep into low level programming, operating system and hardware principles.
I distinctly remember having the same experience. For some reason I believed dynamic variable naming was a good idea. What was I on??