Is This The End?

Sandra Escalante
3 min readApr 19, 2021

When I look back to my first day of class, I am proud of how far I’ve come. I used to think that websites were built with complicated language that was mysterious and inaccessible to someone like me. Now, I see that it is most definitely a complicated language, but incredible accessible to someone like me. Not only do I understand it, but I can make it look pretty! When I started class, I made sure to block out time for me to play with different websites and explore other developers work. Seeing what others create in not only inspiring, but helps me understand how to build a great website.

Beyond coding, I feel like I have gained a community. My classmates are really great people who, like me, are just wanting to better their lives. We are all on the same Discord server and it feels like I have new friends who support me and understand what I’m going through.

My future is looking positive. If I can understand this next Javascript course, I feel confident that I can make it in this industry. I still have a long way to go, but creating a better life is driving me to succeed. When I’m not in class, I am building practice websites and watching what other people in the industry are doing. I hope that when I finish bootcamp, my portfolio will be strong enough to get an entry level job somewhere that will value my work and pay better. In ten months, I hope I am working in a better environment building websites and developing apps.

The main reason as to why JS files are linked at the bottom of the body is because whenever a browser encounters any JS, it parses it and executes that on the spot. Hence, if it was to be added at the top, it would make the page rendering slow and thus it would take more time for page load. Moreover since the DOM won’t be rendered fully, JS won’t be able to manipulate the elements. On the contrary, CSS files are linked in the head because they get applied regardless of DOM already rendered or not.

The building blocks of HTML5 are:

Semantics — Allowing you to describe more precisely what your content is.

Connectivity — Allowing you to communicate with the server in new and innovative ways.

Offline and storage — Allowing webpages to store data on the client-side locally and operate offline more efficiently.

Multimedia — Making video and audio first-class citizens in the Open Web.

2D/3D graphics and effects — Allowing a much more diverse range of presentation options.

Performance and integration — Providing greater speed optimization and better usage of computer hardware.

Device access — Allowing for the usage of various input and output devices.

Styling — Letting authors write more sophisticated themes.

You only need to remember one thing: “nth-child” selects the child element of the parent element. This child element does not specify the exact type. It will be effective when two conditions are met at the same time: one is a child element, and the other is The child element happens to be at that position; “nth-of-type” selects a child element of a parent element, and this child element is of the specified type.

If there are two or more conflicting CSS rules that point to the same element, the browser follows some rules to determine which one is most specific and therefore wins out. Think of specificity as a score/rank that determines which style declarations are ultimately applied to an element.

I use several resources to learn about front-end development and design. It usually starts with a You Tube rabbit hole and ends with me saving about ten new websites to my bookmarks. CSS-Tricks has been incredible helpful but I would be so lost without W3 Schools. That has been my main resource.

--

--