Starting with HTML
HTML, short for HyperText Markup Language, is where I initially started my journey many years ago by altering my Tumblr blog templates to better suit my style. HTML is a markup language used to structure and organize web content. It defines the structure of web pages by using a series of elements and tags which are then interpreted by web browsers to display content correctly.
When I initially started learning HTML, it taught me to alter the content of the page. More specifically, it allowed me to specify how different types of content, such as text, images, audio, etc., should be displayed. When I had reinvigorated my learning of programming (the whole story can be read here), this is where I started - I had several reasons why I started here, which I didn't understand initially, but that have become clearer as time has passed.
For one, HTML is the foundation of the web - it is the standard markup language used for creating pages as well as web applications. In addition, it is easy to learn and use. The syntax is simple and uses familiar elements (headers, paragraphs, lists). From a developer's standpoint, HTML is essential for SEO as search engines use the structure and content of a webpage, defined as HTML, to understand the content and context of a page.
What was the first task I tackled using HTML? Writing out the content of a brownie recipe web page, as seen below.
<html lang="en"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=edge"> <meta name="viewport" content="width=device-width, initial-scale=1.0"> <title>Document</title> </head> </body> </html> <h1>Deep Dish Brownies</h1> <img src="https://img.buzzfeed.com/video-api-prod/assets/fafe8090b4f3434f80c33b6e4ce40e24/BFV21539_BestFudgyBrownies-ThumbB1080.jpg" alt="Brownies"> <h4>Recipe by: Biz McMahon</h4> <h2>Related Recipes</h2> <ul> <li><a href="#">Chewiest Brownies</a></li> <li><a href="#">Can't Tell They're Low-fat Brownies</a></li> <li><a href="#">Bodacious Brownies</a></li> <li><a href="#">Katrina's Best-Ever Chocolate Brownies</a></li> <li><a href="#">Easy Fudge Brownies</a></li> </ul> <h2>Prep Time</h2> <span>60 mins</span> <h3>Servings</h3> <span>9</span> <h2>Ingredients</h2> <ul> <li>3/4 cup butter, melted</li> <li>1 1/2 cups white sugar</li> <li>1 1/2 teaspoons vanilla extract</li> <li>3 eggs</li> <li>3/4 cup all-purpose flour</li> <li>1/2 cup unsweetened cocoa powder</li> <li>1/2 teaspoon baking powder</li> <li>1/2 teaspoon salt</li> </ul> <h2>Directions</h2> <ol> <li>Preheat oven to 350 degrees F (175 degrees C) and Grease an 8 inch square pan.</li> <li>In a large bowl, blend melted butter, sugar and vanilla.</li> <li>Beat in eggs one at a time.</li> <li>Combine the flour, cocoa, baking powder and salt. Gradually blend into the egg mixture.</li> <li>Spread the batter into the prepared pan.</li> <li>Bake in preheated oven for 40 to 45 minutes, or until brownies begin to pull away from the sides of the pan.</li> <li>Let brownies cool, then cut into squares. Enjoy!</li> </ol> <h3>Tip</h3> <p>Aluminum foil can be used to keep food moist, cook it evenly, and make clean-up easier.</p> <h6>Nutritional Info</h6> <span>340 cals</span> <p>Find this recipe <a href="http://allrecipes.com/recipe/11063/deep-dish-brownies">here</a></p>
Styling with CSS
Just like my experience with HTML, I originally used CSS, or Cascading Style Sheets, to fiddle around with colours and text sizes. CSS describes the look and formatting of a document written in HTML. It is an important part of modern web development because it allows developers to separate the content of the webpage (HTML) from its presentation (CSS). Because of this, I was able to create a web page that not only contained the content I wanted, but that looked good as well.
CSS, while able to make things look good, has other benefits. It allows you to centralize styling information for a website, so you don't have to repeat the same styling constructions for every webpage and element. Furthermore, it allows for greater control over the appearance of a website. CSS grants fine-grained control over the look and feel of a website by specifying different styles for various elements, devices and screen sizes. That means you can create a responsible and adaptive website that looks great on any device.
Using CSS can improve the performance of a website since it can minimize the use of HTML tags, as it allows you to define styles for multiple elements in a single stylesheet, rather than repeating the same styles for each element in the HTML. In addition, it allows the browser to apply the styles to the web page without having to parse and apply the styles directly in the HTML. Since the HTML document will be smaller and more streamlined and the browser only has to read and apply the styles once, versus for each element in the HTML document, this improves the overall performance of the web page.
To get a better understanding of how HTML and CSS interacted, I spent some time cloning some popular websites, TechCrunch, BBC and Khan Academy, to better understand how the content and styling of the website interacted with one another.
In addition to front and back-end development, JS also excels at tasks such as testing, automation and deployment. There are frameworks like Mocha and Jasmine to test your code, and tools like Grunt or Gulp to automate tasks such as minification and optimization. JS can also create interactive data visualizations using libraries like D3.js, making it easier to understand and analyze data.
You can find more on my GitHub.
Where data structures and algorithms come in
Entering web development, I thought I would just create some pretty websites or useful applications or potentially contribute to software that I enjoy using myself. The development of applications requires some foundational knowledge of data structures and algorithms (DSA). So what are they and why are they important?
Data structures specialize in storing and organizing data in a specific way that enables efficient access and modification. Algorithms, on the other hand, are step-by-step procedures to solve a problem or achieve a goal. They are typically designed to be executed by a computer but they can also manipulate data structures as well as perform tasks such as searching, sorting and pattern matching.
In programming, DSAs are important because they provide the foundation for efficient and effective problem-solving. Choosing the right DSA for a given task improves the performance of the program - something that is otherwise known as Big O Complexity.
Big O Complexity is basically a measure of efficiency used to describe performance. Big O, where the O stands for "order of growth" is also used to determine the worst-case scenario to see how well things will perform under different conditions. The two aspects of Big O are time, which assesses how long it will take for the function to execute, and space, which looks at how much space will be taken up.
Now, why is this needed and why should you have a good understanding? Some will say it's to pass the interviews and, to a point, that's true. In pursuing a career in software you must understand DSA as they are commonly involved in the interview process - specifically they're a part of technical tests. However, there is more to it than just passing a technical test.
DSA forms the foundation of computer science and is used in many areas of software development including database systems, operating systems and computer networks. Knowing how different DSAs can help you make more informed decisions lead to more efficient and effective solutions.
What I learned
While learning these topics, I discovered that learning and building in tandem were what worked best for me. I managed to learn the fundamentals of some important topics as well as build projects to showcase my skills. I did all of this while expanding my understanding of the nuances of each aspect and creating a solid foundation before moving on to the next task.
Each project taught me something different, each topic introduced me to a world of opportunities. Having learned things this way, I feel that going forward I can easily apply what I know to other languages to better pick things up.
I'm currently focusing on building some more involved projects with the stack I have now, as mentioned above, all while growing my understanding of DSAs.
Isn't learning fun?
Did you find this article valuable?
Support Sarah Gerrard by becoming a sponsor. Any amount is appreciated!