DEV Community: Anubhav Jain

HTML Head and Metadata

Anubhav Jain — Wed, 10 Aug 2022 14:21:50 +0000

HTML head is the part of an HTML document that never actually shows up on a webpage. Why then, do we make an effort to write it? Well, the job of the <head> tag is not to display stuff on the screen, but to serve the metadata about the webpage.
What is metadata, you ask? Well, metadata is data about the data. It is the data that describes what the data being served actually contains. It is usually not meant for humans though. The <head> tag contains information that helps machines understand what a webpage contains. We will talk about it soon.

Lets go by the most used tags inside HTML head tag-

<title>- The <title> tag is probably among the top five most well-known tags of an HTML page. It contains the text that is displayed on the tab as the name of the page. It is also the text that shows up as the name when we bookmark a tab in our browsers.
<link>- This is the tag we use to link our CSS styles to our webpages.
For example-
<link rel="stylesheet" href="my-css-file.css">
<script>- The tag to link the all-encompassing javascript files to our webpages. This tag however comes with a catch. We should use the keyword defer when using this tag inside <head>.
For example-
<script src="script.js" defer></script>
What defer does is tells our webpage to load the javascript after the html and css files have finished loading. This is because javascript takes time to load which may cause our webpage to take a longer time to load on browsers. This is turn, reduces our webpage's SEO score and cause our website to visible to fewer and fewer people. And we don't want to be in the second page of Google Search now, do we?
lang- This attribute is used along with the opening <html> tag.
<html lang="en-US">

While this tag is often overlooked by beginner web developers but it is very important as search engines are better able to index our webpages when the lang attribute is present.
<meta>- Although everything inside the <head> tag is already a part of the metadata, HTML provides an official way of adding metadata to our webpages. This is where <meta> comes in. It helps us add several types of metadata to our webpages.
- charset- charset is something we use to set the character encoding for our webpages. We use it to tell the browser what convention to follow to convert digital data from binary to decimal to character form.They are of different types such as ANSI, ASCII or UTF-8.
- name and content- these attributes are used with meta tags to set the properties such as name of the author, description of the file and stuff like that. For example- <meta name="author" content="Anubhav Jain"> Such tags are pretty helpful for SEO or in case someone wants to know who developed a particular page.
Favicons- another way of enriching our webpages is adding a small icon to our page. These are small but good features to have in our webpages.

For example-

<link rel="icon" href="favicon.ico" type="image/x-icon">

Well, that's it folks! If it helps, do like this post. If you would like to reach out, you can find me on LinkedIn or Twitter

Git

Anubhav Jain — Tue, 02 Aug 2022 12:12:58 +0000

Git is probably one of the most used tools by programmers. While it is the most used tools, it is also a bit difficult to grasp by beginners. I wrote this tutorial in order to give you an overview of git and understand how to use its various features.

Suppose you work in a bakery making cakes for customers. The bakery here represents the organization you are working for. Now, you probably aren't the only one working there. There are others alongside you who make cakes as well. All the bakers use the bakery's common storeroom to get the ingredients required to make the cakes. The storeroom here represents the master code or the main code that everyone uses to develop new features or fix existing code.
Imagine how troublesome it will be if all the bakers took the same ingredients and started working on making the same cake all at once. Someone might add extra sugar or not add some other ingredient, resulting in a horrible tasting cake.
This is where the branching feature of git comes into play. All the bakers take the same ingredients from the store and start working on their individual cakes in their individual kitchens based on different customer's requirements. In other words, all the engineers are making changes to the same code without being affected by what others are doing. This in short, is what is probably the most famous feature git has to offer. If you are with me till now, keep reading!

Now, once the cakes are ready, we can't just send it out to the customers without any review. We take our peers' help to make sure the cake is beautiful to look at as well as the taste is up to the mark. This is what engineers do when they raise a pull request.
They ask their peers to review their code and suggest our changes before merging the code into a release branch. Once, it is in a release branch, it is tested once again to make sure we did not miss out on any issues that may pop up later and irritate the customer.

Now, how to make sure that our code is used up by other software engineers when they write new features to the codebase? We merge our branch with the master. Now, when someone uses the master code to start development. Our code will be present in there as well. Simple!

ChatBot

Anubhav Jain — Wed, 20 May 2020 06:36:57 +0000

Hey everyone.
This is my first post here. I recently built a generative chatbot using keras. The chatbot uses LSTMs and dense layers to provide output to the user. The chatbot is currently text-based, however, I plan to add text-to-speech to it as well.