"Do you have any advice on finding a job as a developer?"

Many people have asked me that question, but I can’t give a proper answer because I have never been hired as a developer before. I'm horribly equipped to answer questions about finding a job.

But Chris Lienert is great at it. Chris has experience hiring and building teams of excellent developers. And he has lots of golden nuggets to share with you in this episode.

If you don't want to commit a file into a Git repository, it makes sense not to have the file show up in the staging area.

You can do this with a Gitignore file.

There are four types of files you should not commit into your Git repository.

1. Files that don't belong to the project

2. Files that are automatically generated

3. Libraries (depends on the situation)

4. Credentials

We use Git tags to create releases. In this video, you'll learn how to tags manually without Git Flow.

Collaborators can decide whether to accept or reject your pull request. They may also request for some changes. This episode shows you how the reviewing and process looks like.

When you want to contribute to a repository, you need to submit a pull request. This video explains what a pull request is, and how to submit one.

Git stashes can be used to temporarily store code you don't want to commit. This episode shows you how to create and apply Git Stashes.

When we use Semantic versioning, we let developers know whether a change will break their code. This episode explains what Semantic Versioning is and how to use it.

Git flow is a well-known method to manage your git branches. You'll learn how to use Git Flow in this video

Imagine there are parallel worlds. We have:

1. A world where I have created this video, and you're watching it.

2. A world where I have created this video, but you're not watching it.

3. A world where I did not create this video.

In this parallel world concept, a Git branch is a parallel world.