When you begin to program for the first time these things you need to know.

1. You see something new. You see a new keyword, you see a new way of things worked out. Once you have seen it, it is unclear how it works exactly.

2. So you try to know how it works. How exactly it performs and what all it does. This is a very abstract or simple definition of how it works.

3. Then you begin to see how it is used. This is where you are familiar with what it is and how it works. So you now see how it works.

4. The next thing is to remember how it works and find a place to use it to work. For you to use something well, you need to understand how something works and how far or how much it works. Then you can find a way to use it and make it work.

5. What to use and when to use depends on what kind of processing you are deciding to do with the data. The data types may have limited functionality and so using a particular data type may limit your ability to process it to produce a desired output. Depending on what you want to get output you need to go backwards and ask looking at the input that what options do I have to process this input to get my output.

6. Sometimes limited concepts make it hard to implement certain aspects of the program. Sometimes you need more concepts to execute a context. Sometimes you need more build examples to understand how it blends into different parts of the program.

7. Moving from one part of program to another and making the logic work to get what you want requires a work-till-you-get-it-right approach. You may need to look at the things you did again. Some concepts need revision.

8. I had a doubt why id's and classes both of them exist as css rules. Let me give an example on how it is used. So I had two textarea inputs and both of them needed to look the same so I declared a common class for them in css rules. But when I decided to make the project interactive. I realized that one text area needed the javascript to talk to it to get the input and other textarea needed to talk to the javascript to get a value. Obviously javascript could not talk to them uniquely unless I declared an id for both. So I had to declare an id for both. This helped javascript to talk to both of the textareas well.

9. So it takes time to make sense why everything exists. At the very basic you have to do one or two things but to make it work you may need to keep adding things in terms of requirements as dictated by limitations in terms of input gathering, processing requirements, output display requirements, ease of usage and to make it look decent enough to engage with it.

10. Take time to know why it's done and the different use cases implementation will help you to explore more instead of making you feel it's too much.