Thanks for the suggestion. I will look into the book. is there an online resource which explains the hashmap algorithm to beginners? I think I can get the CLRS algorithms book from a friend. Does that have a good breakdown? I do understand most of the Python syntax I have encountered but being self taught, I don't have any background in how algorithms like the hashing one are constructed.
CLRS is a great book if you can understand it.
The bold is pretty much part of that nebulous area I spoke of that no one's online site has really figured out how to address.
Honestly how I would approach it is, enter the code line for line regardless if any of it makes any sense to you or not. Write down in the comments what does make sense to you and/or what you think that particular piece will do. Step back and look at the code as a whole, taking a guess on what it's suppose to do. For the portions that make no sense to you, go back and read up on it and do exercises focused on it (Example, if you don't really understand hashes, find another source that focuses on hashes at an introductory level).
I think the problem many websites/books have self taught people run into is the idea that programmers know everything about programming and when they sit down they will code into existence. It's why I recommended that Computer Science Basic Programming book to you. It helps build the mindset of looking at the problem you're trying to solve, writing the steps in plain English, then pseudo code, then real code.
You basically have to break out of the "human" mindset on how to do things/write instructions and realize computers need literal instructions for every step.
Example, if I asked you how to make peanut butter and jelly sandwich. You'd probably say something like "get two pieces of bread, spread PB on one, and jelly on the other, combine them then eat". If you gave those instructions to a computer nothing would be done. What is Peanut Butter? It needs to be defined, as does Jelly, as does bread these are objects, spreading the jelly onto the bread, how? That's a function (one or more), etc.
One thing I always hear people suggest is writing down your activities step by step as a way of practicing. Breaking down the object, the parameters/arguments, the functions needed etc.
I also suggest doing code katas in ever increasing difficulty. It might be hard as hell, but once you get one or two you'll start to figure things out. Things will start to click, and at that point you're slowly exiting that nebulous area I spoke of earlier.
These two are TDD based so you're not going in blind.
exercism.io
codewars
