• Use search engines as a resource to find information
• Identify relevant resources
• Compare multiple resources to find the best source

When writing HTML you might encounter tags that are new to you. How are we going to level-up? When searching for technical help, we have to be careful about which sources we trust. This is a skill you will build over time, but we'll model some good practices in this README.

Let's say in your research, you come across an unfamiliar HTML element like <samp>. We can google samp html element, and we will find an endless list of results to choose from. Sometimes resources can be outdated, biased, or inaccurate. It's important to filter through the results to find the best fit.

Your instinct might be to open the first result. You should be pickier. Sometimes the result has "gamed" the search engine and unfairly influenced the ranking. We recommend that you open the top five results and review them critically.

We also recommend that you trust sites that are affiliated with building or defining the technologies more than blogs or other resources. In the HTML world, the Mozilla Developer Network (MDN) is an extremely trustworthy site. In fact, it's likely the best HTML, JS and CSS documentation source on the internet.

If we go back to the search results, you'll see that the first result, in this case, is W3schools. A site, like W3schools, for example, can be used as an additional resource for garnering understanding. It even includes interactive examples, creating a sandbox environment for experimentation.

In this case, between MDN and W3schools, you should get a good sense of how to use the <samp> element.

The web is a constantly evolving entity. As we build more ambitious products or learn from our collective needs and mistakes, the industry will continually update the HTML specifications.

Researching referencing documentation can be scary at first, but it's a primary skill for developers. Don't be afraid to practice technical searches. It's a skill that you will get better at with practice.

Most importantly, don't feel like not knowing everything by heart means you can't be a developer. The greatest developers we know are constantly admitting what they don't know, finding the latest news, using the answer they found and moving on.