Getting Started With Version Control System; Git and Github.

Taiwo Oluwaseyifunmi — Sun, 07 Feb 2021 21:05:44 +0000

A version control system(VCS) is a software tool that allows you to document changes made to files by keeping a track of changes to a coding block. It is a program that allows you to monitor or handle multiple versions of your source code updates. Version control system helps you understand who made changes, what changes, when the changes were made, and many more.

My very simple analogy for understanding this better is saying the words "version control" backward which gives you "control version" and in this case, "control version" would also mean "back up". This encourages you to make improvements to your coding projects without fear. The key idea of a version control system is to help preserve a detailed project history and its numerous future improvements/modifications. Another name for a version control management method is source code manager(SCM).

It is imperative that we are aware that "version controls" form a part of our daily lives. For example, you don't consciously keep different copies of a document when you type, but your computer does! A major reason why you can "ctrl + z" to dismantle an action when you make errors. Another great scenario is having to retrace your steps whenever you lose something on your way.

So, who can use a VCS?
Versioning(adj.) is a coding practice that should be used by both individual coders and any group of people involved in a project. It helps to keep code organized, clean and changes, traceable.

What are the benefits of Version control systems?
Version control systems help developers do the following:

Understand better the changes made to projects by keeping track of who, where, and why adjustments were made.
Foster the remote working culture.
Helps developers take screen breaks and time away from monospace fonts without fear.
Maintenance of multiple code variants.
Have complete backups to their projects without occupying much space.

Moving on, there are three version control models. Just like we have various operating systems and myriads of devices running on each one, the same thing we've got running for version control systems. There are three version control models, each of which has different version control software using them.

Types of version control system models:

Local Version Control System: in this model, all developers on the project have access to only one copy of that project. Meaning that if any changes were to be, the developers have to manually make a copy of that file before making changes to it.
Centralized Version Control System: this is a model where you have to save the snapshot of the application on the server, with history changes saved in the server. This model requires that all developers have access to the files via the internet of a local network. SVN is an example of a centralized version control system, also known as "Apache Subversion".
Distributed Version Control System: In this model, each developer works directly with their own local repository, and changes are shared between repositories as a separate step. Distributed VCS is the inverse of centralized VCS, it gives all the manageable/traceable of the project in the developer/client-side, not server-side. You can check out the branch without connecting to the server, you can also commit changes, trace changes that you have made even without an internet connection. Git is an example of a distributed version control system and has an emphasis on speed and performance. Git is an example of a distributed version control system and has an emphasis on speed and performance.

Git And Github.

There is an erroneous assumption that Git and Github or that Git is simply a funky way of saying Github, especially among noob devs. Git and Github are in fact, two separate entities.

Git is a free and open-source distributed version control system like I earlier mentioned that helps you manage and keep track of your source code changes. Github on the other hand is a cloud-based service that helps developers manage Git repositories (repositories store instances of your code work). From production down to shipment, Github and Git help build collaboration directly into the development process.

Git installation guide
If you already have git installed, that is no problem but if not you can download it here
To open an account on Github, you can sign up here

Git Jargons

Whether as a complete beginner or an experienced developer, you are eventually going to speak the Git language - which sounds super cool. I have highlighted a few of the most common Git commands you'll frequently come across as a developer.

Repository: Sometimes called 'repo' contains the collection of the files making up a project as well as the history of changes made to those files. Repositories in Git is considered as your project folder.

Branch: a branch in Git is a way to keep developing and coding a new feature or modification to the software and still not affecting the main part of the project. It is an essential feature available in most modern version control systems. A Git project can have more than one branch. We can perform many operations on Git branch-like rename, list, delete, etc.

Master: Master is a naming convention for Git branch. It's a default branch of Git. This branch is called a "master" branch because it is a repository's "default" branch.

Remote: In Git, the term remote is concerned with the remote repository. It is a shared repository that all team members use to exchange their changes. A remote repository is stored on a code hosting service like an internal server, GitHub, Subversion, and more.

Git clone: The git clone command generates a local duplicate of an existing project just as its name suggests. The clone operation provides the remote repository with a case. The clone holds all project data, history, and divisions and helps you to copy files of other nations

Pull: The term Pull is used to receive data from GitHub. It fetches and merges changes on the remote server to your working directory. The git pull command is used to make a Git pull.

Pull requests: They are a process for a developer to notify team members that they have completed a feature. Once their feature branch is ready, the developer files a pull request via their remote server account. Pull request announces all the team members that they need to review the code and merge it into the master branch.

Push: The push term refers to upload local repository content to a remote repository. Pushing is an act of transfer commits from your local repository to a remote repository. Pushing is capable of overwriting changes; caution should be taken when pushing.

Git is very useful and important to learn if you want to level up in the tech field. You can watch tutorials on YouTube to learn more. Later on, I will make the second part of this article with advanced commands.

Dealing With Impostor Syndrome.

Taiwo Oluwaseyifunmi — Sun, 10 Jan 2021 18:48:17 +0000

"You're not good enough", "you lack adequate knowledge to teach these kids", "Nigerians speak bad English", "how would you cope?" -these thoughts ran effortlessly through my head whenever I tried to chart a course for my new engagement.

I recently volunteered to teach some London-based kids the rudiments of web development. You would expect me to feel elated about this, I wasn't. Rather I suddenly felt unfit and inadequate for the task. At that moment, I knew it was here again - the impostor syndrome.

What is Impostor Syndrome?

It is a psychological pattern in which an individual doubt their skills, talent or accomplishments and has a persistent internalized fear of being exposed as a fraud. In a simple term, it is the feeling of not belonging and the idea that you have succeeded due to luck, and not because of your talent or qualifications.

How to manage Impostors Syndrome:
The journey of managing impostor syndrome is a thousand-mile that begins with a step. Impostor syndrome isn't something that can be managed immediately, it is a gradual process. There is the "Flywheel Effect" which maintains that anything we do, any effort we put in a venture, a creative process or code is not a waste. It might feel like we're not making progress but that's not the case. Each attempt we make brings us closer to our goal. Hence, be proud of your little progress and do not give impostors syndrome a chance. Here are ways impostor syndrome can be managed:

Take a break: life isn't always going to go according to the plans we have in our head. Good things and bad things happen. When the bad things happen it is okay to take a break. Go visit friends, see a favourite movie, have fun; then come back to the code or whatever you were doing.

Get yourself a support system: when imposters syndrome sets in, it is necessary to have a group of people or friends who you can talk to. People who are positive and will always try to cheer you up when you're down. Surround yourself with friends with whom you can grow together and mentors who are ready to help.

Never compare yourself with anyone: No two human being is going to live life the same way. This can be hard because I know some situations will arise where you can't help it but please try not to. Just like we all have different faces, we all have a different journey. Comparing yourself with your fellow developer or friend has no advantage, it only wastes your time, ruins your chances of learning from such person, ruins the relationship and takes away your joy.

Think positively: always try as much as possible to have positive thoughts. How can you go about this? Personally, I write positive or motivational quotes on sticky notes and I paste them on the walls in my bedroom. So whenever I wake up, I'm waking up to an inspiring message or a bible text that talks about how beautifully and wonderfully made I am or how God has good plans for me.

Develop a healthy response to failure: instead of beating yourself up for falling short, move on, reminding yourself that you're going get it in no time. After all, Henry Ford said " failure is the only way to begin again more intelligently".

All in all, know that there's no growth without sacrifice. Find your voice/path/stack and grow little by little. Have fun, learn to love code, learn to love your craft, be proud of your progress and remember that there's no better you, than the you that you are and watch yourself rise to the peak of your career.

DEV Community: Taiwo Oluwaseyifunmi

Getting Started With Version Control System; Git and Github.

Git And Github.

Dealing With Impostor Syndrome.

What is Impostor Syndrome?