The Importance of Git and GitHub

Today is the first day of my coding boot camp, and so far it had been a fun challenge. The concept for today was to learn how to use Git and GitHub.

As a prospecting developer, the instructors stressed the importance of learning how to traverse and read our file system within the computer. There are two types of methods that we can use to navigate our file system: Graphical User Interface (GUI) and command line interface (CLI). If you own a Microsoft laptop, you would find that you can navigate your files via GUI simply by clicking on a Document folder or even a Music folder. However, on the other hand, you use CLI via the terminal to access these files as well. “The CLI provides a text-based interface that utilizes a special programming language called “Bash.” The CLI is considerably more powerful than Finder, and most programmers prefer it for managing projects and for interacting with tools like Git” (The Iron Yard).

Since I was used to Graphical User Interface, it was time to use the command line interface and make that second-nature to me in terms of using it and writing codes.

As it turned out, Git is a program where it allows people to create codes on their local repository. When the code meets the developer’s satisfaction, then they can push that code to the remote repository which is where GitHub comes in. Keep in mind–any changes we do to the codes within Git, it does NOT affect what happens to the codes in GitHub. GitHub is a great tool to use for developers to collaborate on a single project. It not only allow us to push our code into the remote repository, it also allows us to pull that code from the remote repository into our local repository to see what we can work with.

The Iron Yard not only uses us the ways of using Git and GitHub via terminal, they also teaches us the best practices of how to handle collaboration. That’s why when I learned how to create my own local and remote repositories–I also learned to collaborate with others using my local repository to a single repository that other developers are using as well. We needed to learn how to communicate the technicality of pushing, pulling, adding, deleting files and folders.

It made me feel good knowing that there is a website that serves to make collaboration between developers a smooth ride. Sure–there will be a stumble here and there, but that’s the point of collaboration–we just need to step away from the computer and discuss with other developers in person to see what we can do to make it work!

There’s several more concepts that I learned regarding Gits and GitHubs but I will get to those in later post as well.

Otherwise, this post would’ve become an extremely long post!


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

Powered by

Up ↑

%d bloggers like this: