This week was quite interesting. For starters, the only thing I understood about JavaScript coming into this course was that it was difficult to understand (compared to HTML/CSS). But I didn’t exactly know what I didn’t know.

This week’s lessons were useful for showing us what JavaScript is used for, from adding and subtracting to serving as a foundational tool for bigger-picture project display. I’m definitely going to have to go through the lessons again (and again) to remember how the consoles work with each other (and sometimes exist inside each other, which was confusing at first). But overall, it was pretty clear.

Seeing how if/then questions are answered through programming was also interesting. I always knew that behind responsive design, some programming logic has to be in place for the page’s display to adjust to whatever the user is doing. Starting from smaller if/then statements and then building and adding conditions for more complicated, data-laden graphics is neat, and it gives me a whole new appreciation for the work my office’s developers do on a daily basis.

One question I have, though, is about the commenting language within the script. Since it’s expected for us to link HTML/CSS/JavaScript pages together, why are smaller functions (such as the invisible commenting function) not consistent across the board? Wouldn’t it be reasonable for some of the rudimentary labeling factors to be consistent?

Other than that, I am appreciative of the in-depth comments on my previous assignment. Things are looking much clearer now with regards to page organization. In fact, I was originally not as concerned about having clean (perfectly and consistently indented) text on my code page as long as it works. Now, I see that unorganized work (even if it displays exactly what you’re looking for on the front end) is a bad habit that will result in unnecessary frustration as the page gets more and more jumbled.