When to Delete branches?

Normally in a contribution flow Branches are a great way to work on different features, fixes, etc. while isolating them from the main codebase. So a repo may have a master branch, and separate branches to work on different features.

Typically once the work is completed on a feature and it is recommended to delete the branch.

The Delete workflow:

Lets say you have a repo called as AwesomeRepo, and its hosted on Github, at a location such as https://github.com/my_username/AwesomeRepo.

Also lets assume it has the branches like: <br>master<br>feature/some-cool-new-stuff<br>fix/authentication<br>staging<br>

For consistency we will assume branch names are same on local as well as on the remote.

Now, lets say you are done with that fix for authentication and want to remove the branch fix/authentication.

When to Delete branches?

Normally in a contribution flow Branches are a great way to work on different features, fixes, etc. while isolating them from the main codebase. So a repo may have a master branch, and separate branches to work on different features.

Typically once the work is completed on a feature and it is recommended to delete the branch.

The Delete workflow:

Lets say you have a repo called as AwesomeRepo, and its hosted on Github, at a location such as https://github.com/my_username/AwesomeRepo.

Also lets assume it has the branches like: <br>master<br>feature/some-cool-new-stuff<br>fix/authentication<br>staging<br>

For consistency we will assume branch names are same on local as well as on the remote.

Now, lets say you are done with that fix for authentication and want to remove the branch fix/authentication.

When to Delete branches?

Normally in a contribution flow Branches are a great way to work on different features, fixes, etc. while isolating them from the main codebase. So a repo may have a master branch, and separate branches to work on different features.

Typically once the work is completed on a feature and it is recommended to delete the branch.

The Delete workflow:

Lets say you have a repo called as AwesomeRepo, and its hosted on Github, at a location such as https://github.com/my_username/AwesomeRepo.

Also lets assume it has the branches like: <br>master<br>feature/some-cool-new-stuff<br>fix/authentication<br>staging<br>

For consistency we will assume branch names are same on local as well as on the remote.

Now, lets say you are done with that fix for authentication and want to remove the branch fix/authentication.

Coding Help

I started this list while doing Algorithms, noticing a few things that were common issues / questions but I think most of them are going to be useful to people coding in general. If you've got some tips to help people code I'd love to hear them.

If you don't know where to start, write some pseudocode. Plan out the logic you're trying to implement in your native language before you try to put it into code.

Comment your code! Can't stress that one enough, if you get lost or take a break then come back you need to know what your code is trying to do. It will also reinforce what the code means to you, and help other people understand what your code does if you get stuck and ask for help. If you've got a any other tips for campers I'd love to see them!

When to Delete branches?

Normally in a contribution flow Branches are a great way to work on different features, fixes, etc. while isolating them from the main codebase. So a repo may have a master branch, and separate branches to work on different features.

Typically once the work is completed on a feature and it is recommended to delete the branch.

The Delete workflow:

Lets say you have a repo called as AwesomeRepo, and its hosted on Github, at a location such as https://github.com/my_username/AwesomeRepo.

Also lets assume it has the branches like: <br>master<br>feature/some-cool-new-stuff<br>fix/authentication<br>staging<br>

For consistency we will assume branch names are same on local as well as on the remote.

Now, lets say you are done with that fix for authentication and want to remove the branch fix/authentication.

When to Delete branches?

Normally in a contribution flow Branches are a great way to work on different features, fixes, etc. while isolating them from the main codebase. So a repo may have a master branch, and separate branches to work on different features.

Typically once the work is completed on a feature and it is recommended to delete the branch.

The Delete workflow:

Lets say you have a repo called as AwesomeRepo, and its hosted on Github, at a location such as https://github.com/my_username/AwesomeRepo.

Also lets assume it has the branches like: <br>master<br>feature/some-cool-new-stuff<br>fix/authentication<br>staging<br>

For consistency we will assume branch names are same on local as well as on the remote.

Now, lets say you are done with that fix for authentication and want to remove the branch fix/authentication.

When to Delete branches?

Normally in a contribution flow Branches are a great way to work on different features, fixes, etc. while isolating them from the main codebase. So a repo may have a master branch, and separate branches to work on different features.

Typically once the work is completed on a feature and it is recommended to delete the branch.

The Delete workflow:

Lets say you have a repo called as AwesomeRepo, and its hosted on Github, at a location such as https://github.com/my_username/AwesomeRepo.

Also lets assume it has the branches like: <br>master<br>feature/some-cool-new-stuff<br>fix/authentication<br>staging<br>

For consistency we will assume branch names are same on local as well as on the remote.

Now, lets say you are done with that fix for authentication and want to remove the branch fix/authentication.

When to Delete branches?

Normally in a contribution flow Branches are a great way to work on different features, fixes, etc. while isolating them from the main codebase. So a repo may have a master branch, and separate branches to work on different features.

Typically once the work is completed on a feature and it is recommended to delete the branch.

The Delete workflow:

Lets say you have a repo called as AwesomeRepo, and its hosted on Github, at a location such as https://github.com/my_username/AwesomeRepo.

Also lets assume it has the branches like: <br>master<br>feature/some-cool-new-stuff<br>fix/authentication<br>staging<br>

For consistency we will assume branch names are same on local as well as on the remote.

Now, lets say you are done with that fix for authentication and want to remove the branch fix/authentication.

When to Delete branches?

Normally in a contribution flow Branches are a great way to work on different features, fixes, etc. while isolating them from the main codebase. So a repo may have a master branch, and separate branches to work on different features.

Typically once the work is completed on a feature and it is recommended to delete the branch.

The Delete workflow:

Lets say you have a repo called as AwesomeRepo, and its hosted on Github, at a location such as https://github.com/my_username/AwesomeRepo.

Also lets assume it has the branches like: <br>master<br>feature/some-cool-new-stuff<br>fix/authentication<br>staging<br>

For consistency we will assume branch names are same on local as well as on the remote.

Now, lets say you are done with that fix for authentication and want to remove the branch fix/authentication.

When to Delete branches?

Normally in a contribution flow Branches are a great way to work on different features, fixes, etc. while isolating them from the main codebase. So a repo may have a master branch, and separate branches to work on different features.

Typically once the work is completed on a feature and it is recommended to delete the branch.

The Delete workflow:

Lets say you have a repo called as AwesomeRepo, and its hosted on Github, at a location such as https://github.com/my_username/AwesomeRepo.

Also lets assume it has the branches like: <br>master<br>feature/some-cool-new-stuff<br>fix/authentication<br>staging<br>

For consistency we will assume branch names are same on local as well as on the remote.

Now, lets say you are done with that fix for authentication and want to remove the branch fix/authentication.

When to Delete branches?

Normally in a contribution flow Branches are a great way to work on different features, fixes, etc. while isolating them from the main codebase. So a repo may have a master branch, and separate branches to work on different features.

Typically once the work is completed on a feature and it is recommended to delete the branch.

The Delete workflow:

Lets say you have a repo called as AwesomeRepo, and its hosted on Github, at a location such as https://github.com/my_username/AwesomeRepo.

Also lets assume it has the branches like: <br>master<br>feature/some-cool-new-stuff<br>fix/authentication<br>staging<br>

For consistency we will assume branch names are same on local as well as on the remote.

Now, lets say you are done with that fix for authentication and want to remove the branch fix/authentication.

When to Delete branches?

Normally in a contribution flow Branches are a great way to work on different features, fixes, etc. while isolating them from the main codebase. So a repo may have a master branch, and separate branches to work on different features.

Typically once the work is completed on a feature and it is recommended to delete the branch.

The Delete workflow:

Lets say you have a repo called as AwesomeRepo, and its hosted on Github, at a location such as https://github.com/my_username/AwesomeRepo.

Also lets assume it has the branches like: <br>master<br>feature/some-cool-new-stuff<br>fix/authentication<br>staging<br>

For consistency we will assume branch names are same on local as well as on the remote.

Now, lets say you are done with that fix for authentication and want to remove the branch fix/authentication.

When to Delete branches?

Normally in a contribution flow Branches are a great way to work on different features, fixes, etc. while isolating them from the main codebase. So a repo may have a master branch, and separate branches to work on different features.

Typically once the work is completed on a feature and it is recommended to delete the branch.

The Delete workflow:

Lets say you have a repo called as AwesomeRepo, and its hosted on Github, at a location such as https://github.com/my_username/AwesomeRepo.

Also lets assume it has the branches like: <br>master<br>feature/some-cool-new-stuff<br>fix/authentication<br>staging<br>

For consistency we will assume branch names are same on local as well as on the remote.

Now, lets say you are done with that fix for authentication and want to remove the branch fix/authentication.

When to Delete branches?

Normally in a contribution flow Branches are a great way to work on different features, fixes, etc. while isolating them from the main codebase. So a repo may have a master branch, and separate branches to work on different features.

Typically once the work is completed on a feature and it is recommended to delete the branch.

The Delete workflow:

Lets say you have a repo called as AwesomeRepo, and its hosted on Github, at a location such as https://github.com/my_username/AwesomeRepo.

Also lets assume it has the branches like: <br>master<br>feature/some-cool-new-stuff<br>fix/authentication<br>staging<br>

For consistency we will assume branch names are same on local as well as on the remote.

Now, lets say you are done with that fix for authentication and want to remove the branch fix/authentication.

When to Delete branches?

Normally in a contribution flow Branches are a great way to work on different features, fixes, etc. while isolating them from the main codebase. So a repo may have a master branch, and separate branches to work on different features.

Typically once the work is completed on a feature and it is recommended to delete the branch.

The Delete workflow:

Lets say you have a repo called as AwesomeRepo, and its hosted on Github, at a location such as https://github.com/my_username/AwesomeRepo.

Also lets assume it has the branches like: <br>master<br>feature/some-cool-new-stuff<br>fix/authentication<br>staging<br>

For consistency we will assume branch names are same on local as well as on the remote.

Now, lets say you are done with that fix for authentication and want to remove the branch fix/authentication.

When to Delete branches?

Normally in a contribution flow Branches are a great way to work on different features, fixes, etc. while isolating them from the main codebase. So a repo may have a master branch, and separate branches to work on different features.

Typically once the work is completed on a feature and it is recommended to delete the branch.

The Delete workflow:

Lets say you have a repo called as AwesomeRepo, and its hosted on Github, at a location such as https://github.com/my_username/AwesomeRepo.

Also lets assume it has the branches like: <br>master<br>feature/some-cool-new-stuff<br>fix/authentication<br>staging<br>

For consistency we will assume branch names are same on local as well as on the remote.

Now, lets say you are done with that fix for authentication and want to remove the branch fix/authentication.

When to Delete branches?

Normally in a contribution flow Branches are a great way to work on different features, fixes, etc. while isolating them from the main codebase. So a repo may have a master branch, and separate branches to work on different features.

Typically once the work is completed on a feature and it is recommended to delete the branch.

The Delete workflow:

Lets say you have a repo called as AwesomeRepo, and its hosted on Github, at a location such as https://github.com/my_username/AwesomeRepo.

Also lets assume it has the branches like: <br>master<br>feature/some-cool-new-stuff<br>fix/authentication<br>staging<br>

For consistency we will assume branch names are same on local as well as on the remote.

Now, lets say you are done with that fix for authentication and want to remove the branch fix/authentication.

When to Delete branches?

Normally in a contribution flow Branches are a great way to work on different features, fixes, etc. while isolating them from the main codebase. So a repo may have a master branch, and separate branches to work on different features.

Typically once the work is completed on a feature and it is recommended to delete the branch.

The Delete workflow:

Lets say you have a repo called as AwesomeRepo, and its hosted on Github, at a location such as https://github.com/my_username/AwesomeRepo.

Also lets assume it has the branches like: <br>master<br>feature/some-cool-new-stuff<br>fix/authentication<br>staging<br>

For consistency we will assume branch names are same on local as well as on the remote.

Now, lets say you are done with that fix for authentication and want to remove the branch fix/authentication.

When to Delete branches?

Normally in a contribution flow Branches are a great way to work on different features, fixes, etc. while isolating them from the main codebase. So a repo may have a master branch, and separate branches to work on different features.

Typically once the work is completed on a feature and it is recommended to delete the branch.

The Delete workflow:

Lets say you have a repo called as AwesomeRepo, and its hosted on Github, at a location such as https://github.com/my_username/AwesomeRepo.

Also lets assume it has the branches like: <br>master<br>feature/some-cool-new-stuff<br>fix/authentication<br>staging<br>

For consistency we will assume branch names are same on local as well as on the remote.

Now, lets say you are done with that fix for authentication and want to remove the branch fix/authentication.

When to Delete branches?

Normally in a contribution flow Branches are a great way to work on different features, fixes, etc. while isolating them from the main codebase. So a repo may have a master branch, and separate branches to work on different features.

Typically once the work is completed on a feature and it is recommended to delete the branch.

The Delete workflow:

Lets say you have a repo called as AwesomeRepo, and its hosted on Github, at a location such as https://github.com/my_username/AwesomeRepo.

Also lets assume it has the branches like: <br>master<br>feature/some-cool-new-stuff<br>fix/authentication<br>staging<br>

For consistency we will assume branch names are same on local as well as on the remote.

Now, lets say you are done with that fix for authentication and want to remove the branch fix/authentication.

When to Delete branches?

Normally in a contribution flow Branches are a great way to work on different features, fixes, etc. while isolating them from the main codebase. So a repo may have a master branch, and separate branches to work on different features.

Typically once the work is completed on a feature and it is recommended to delete the branch.

The Delete workflow:

Lets say you have a repo called as AwesomeRepo, and its hosted on Github, at a location such as https://github.com/my_username/AwesomeRepo.

Also lets assume it has the branches like: <br>master<br>feature/some-cool-new-stuff<br>fix/authentication<br>staging<br>

For consistency we will assume branch names are same on local as well as on the remote.

Now, lets say you are done with that fix for authentication and want to remove the branch fix/authentication.

When to Delete branches?

Normally in a contribution flow Branches are a great way to work on different features, fixes, etc. while isolating them from the main codebase. So a repo may have a master branch, and separate branches to work on different features.

Typically once the work is completed on a feature and it is recommended to delete the branch.

The Delete workflow:

Lets say you have a repo called as AwesomeRepo, and its hosted on Github, at a location such as https://github.com/my_username/AwesomeRepo.

Also lets assume it has the branches like: <br>master<br>feature/some-cool-new-stuff<br>fix/authentication<br>staging<br>

For consistency we will assume branch names are same on local as well as on the remote.

Now, lets say you are done with that fix for authentication and want to remove the branch fix/authentication.

When to Delete branches?

Normally in a contribution flow Branches are a great way to work on different features, fixes, etc. while isolating them from the main codebase. So a repo may have a master branch, and separate branches to work on different features.

Typically once the work is completed on a feature and it is recommended to delete the branch.

The Delete workflow:

Lets say you have a repo called as AwesomeRepo, and its hosted on Github, at a location such as https://github.com/my_username/AwesomeRepo.

Also lets assume it has the branches like: <br>master<br>feature/some-cool-new-stuff<br>fix/authentication<br>staging<br>

For consistency we will assume branch names are same on local as well as on the remote.

Now, lets say you are done with that fix for authentication and want to remove the branch fix/authentication.

When to Delete branches?

Normally in a contribution flow Branches are a great way to work on different features, fixes, etc. while isolating them from the main codebase. So a repo may have a master branch, and separate branches to work on different features.

Typically once the work is completed on a feature and it is recommended to delete the branch.

The Delete workflow:

Lets say you have a repo called as AwesomeRepo, and its hosted on Github, at a location such as https://github.com/my_username/AwesomeRepo.

Also lets assume it has the branches like: <br>master<br>feature/some-cool-new-stuff<br>fix/authentication<br>staging<br>

For consistency we will assume branch names are same on local as well as on the remote.

Now, lets say you are done with that fix for authentication and want to remove the branch fix/authentication.

When to Delete branches?

Normally in a contribution flow Branches are a great way to work on different features, fixes, etc. while isolating them from the main codebase. So a repo may have a master branch, and separate branches to work on different features.

Typically once the work is completed on a feature and it is recommended to delete the branch.

The Delete workflow:

Lets say you have a repo called as AwesomeRepo, and its hosted on Github, at a location such as https://github.com/my_username/AwesomeRepo.

Also lets assume it has the branches like: <br>master<br>feature/some-cool-new-stuff<br>fix/authentication<br>staging<br>

For consistency we will assume branch names are same on local as well as on the remote.

Now, lets say you are done with that fix for authentication and want to remove the branch fix/authentication.

When to Delete branches?

Normally in a contribution flow Branches are a great way to work on different features, fixes, etc. while isolating them from the main codebase. So a repo may have a master branch, and separate branches to work on different features.

Typically once the work is completed on a feature and it is recommended to delete the branch.

The Delete workflow:

Lets say you have a repo called as AwesomeRepo, and its hosted on Github, at a location such as https://github.com/my_username/AwesomeRepo.

Also lets assume it has the branches like: <br>master<br>feature/some-cool-new-stuff<br>fix/authentication<br>staging<br>

For consistency we will assume branch names are same on local as well as on the remote.

Now, lets say you are done with that fix for authentication and want to remove the branch fix/authentication.

When to Delete branches?

Normally in a contribution flow Branches are a great way to work on different features, fixes, etc. while isolating them from the main codebase. So a repo may have a master branch, and separate branches to work on different features.

Typically once the work is completed on a feature and it is recommended to delete the branch.

The Delete workflow:

Lets say you have a repo called as AwesomeRepo, and its hosted on Github, at a location such as https://github.com/my_username/AwesomeRepo.

Also lets assume it has the branches like: <br>master<br>feature/some-cool-new-stuff<br>fix/authentication<br>staging<br>

For consistency we will assume branch names are same on local as well as on the remote.

Now, lets say you are done with that fix for authentication and want to remove the branch fix/authentication.

When to Delete branches?

Normally in a contribution flow Branches are a great way to work on different features, fixes, etc. while isolating them from the main codebase. So a repo may have a master branch, and separate branches to work on different features.

Typically once the work is completed on a feature and it is recommended to delete the branch.

The Delete workflow:

Lets say you have a repo called as AwesomeRepo, and its hosted on Github, at a location such as https://github.com/my_username/AwesomeRepo.

Also lets assume it has the branches like: <br>master<br>feature/some-cool-new-stuff<br>fix/authentication<br>staging<br>

For consistency we will assume branch names are same on local as well as on the remote.

Now, lets say you are done with that fix for authentication and want to remove the branch fix/authentication.

When to Delete branches?

Normally in a contribution flow Branches are a great way to work on different features, fixes, etc. while isolating them from the main codebase. So a repo may have a master branch, and separate branches to work on different features.

Typically once the work is completed on a feature and it is recommended to delete the branch.

The Delete workflow:

Lets say you have a repo called as AwesomeRepo, and its hosted on Github, at a location such as https://github.com/my_username/AwesomeRepo.

Also lets assume it has the branches like: <br>master<br>feature/some-cool-new-stuff<br>fix/authentication<br>staging<br>

For consistency we will assume branch names are same on local as well as on the remote.

Now, lets say you are done with that fix for authentication and want to remove the branch fix/authentication.

When to Delete branches?

Normally in a contribution flow Branches are a great way to work on different features, fixes, etc. while isolating them from the main codebase. So a repo may have a master branch, and separate branches to work on different features.

Typically once the work is completed on a feature and it is recommended to delete the branch.

The Delete workflow:

Lets say you have a repo called as AwesomeRepo, and its hosted on Github, at a location such as https://github.com/my_username/AwesomeRepo.

Also lets assume it has the branches like: <br>master<br>feature/some-cool-new-stuff<br>fix/authentication<br>staging<br>

For consistency we will assume branch names are same on local as well as on the remote.

Now, lets say you are done with that fix for authentication and want to remove the branch fix/authentication.

When to Delete branches?

Normally in a contribution flow Branches are a great way to work on different features, fixes, etc. while isolating them from the main codebase. So a repo may have a master branch, and separate branches to work on different features.

Typically once the work is completed on a feature and it is recommended to delete the branch.

The Delete workflow:

Lets say you have a repo called as AwesomeRepo, and its hosted on Github, at a location such as https://github.com/my_username/AwesomeRepo.

Also lets assume it has the branches like: <br>master<br>feature/some-cool-new-stuff<br>fix/authentication<br>staging<br>

For consistency we will assume branch names are same on local as well as on the remote.

Now, lets say you are done with that fix for authentication and want to remove the branch fix/authentication.

When to Delete branches?

Normally in a contribution flow Branches are a great way to work on different features, fixes, etc. while isolating them from the main codebase. So a repo may have a master branch, and separate branches to work on different features.

Typically once the work is completed on a feature and it is recommended to delete the branch.

The Delete workflow:

Lets say you have a repo called as AwesomeRepo, and its hosted on Github, at a location such as https://github.com/my_username/AwesomeRepo.

Also lets assume it has the branches like: <br>master<br>feature/some-cool-new-stuff<br>fix/authentication<br>staging<br>

For consistency we will assume branch names are same on local as well as on the remote.

Now, lets say you are done with that fix for authentication and want to remove the branch fix/authentication.

When to Delete branches?

Normally in a contribution flow Branches are a great way to work on different features, fixes, etc. while isolating them from the main codebase. So a repo may have a master branch, and separate branches to work on different features.

Typically once the work is completed on a feature and it is recommended to delete the branch.

The Delete workflow:

Lets say you have a repo called as AwesomeRepo, and its hosted on Github, at a location such as https://github.com/my_username/AwesomeRepo.

Also lets assume it has the branches like: <br>master<br>feature/some-cool-new-stuff<br>fix/authentication<br>staging<br>

For consistency we will assume branch names are same on local as well as on the remote.

Now, lets say you are done with that fix for authentication and want to remove the branch fix/authentication.

When to Delete branches?

Normally in a contribution flow Branches are a great way to work on different features, fixes, etc. while isolating them from the main codebase. So a repo may have a master branch, and separate branches to work on different features.

Typically once the work is completed on a feature and it is recommended to delete the branch.

The Delete workflow:

Lets say you have a repo called as AwesomeRepo, and its hosted on Github, at a location such as https://github.com/my_username/AwesomeRepo.

Also lets assume it has the branches like: <br>master<br>feature/some-cool-new-stuff<br>fix/authentication<br>staging<br>

For consistency we will assume branch names are same on local as well as on the remote.

Now, lets say you are done with that fix for authentication and want to remove the branch fix/authentication.

When to Delete branches?

Normally in a contribution flow Branches are a great way to work on different features, fixes, etc. while isolating them from the main codebase. So a repo may have a master branch, and separate branches to work on different features.

Typically once the work is completed on a feature and it is recommended to delete the branch.

The Delete workflow:

Lets say you have a repo called as AwesomeRepo, and its hosted on Github, at a location such as https://github.com/my_username/AwesomeRepo.

Also lets assume it has the branches like: <br>master<br>feature/some-cool-new-stuff<br>fix/authentication<br>staging<br>

For consistency we will assume branch names are same on local as well as on the remote.

Now, lets say you are done with that fix for authentication and want to remove the branch fix/authentication.

When to Delete branches?

Normally in a contribution flow Branches are a great way to work on different features, fixes, etc. while isolating them from the main codebase. So a repo may have a master branch, and separate branches to work on different features.

Typically once the work is completed on a feature and it is recommended to delete the branch.

The Delete workflow:

Lets say you have a repo called as AwesomeRepo, and its hosted on Github, at a location such as https://github.com/my_username/AwesomeRepo.

Also lets assume it has the branches like: <br>master<br>feature/some-cool-new-stuff<br>fix/authentication<br>staging<br>

For consistency we will assume branch names are same on local as well as on the remote.

Now, lets say you are done with that fix for authentication and want to remove the branch fix/authentication.

When to Delete branches?

Normally in a contribution flow Branches are a great way to work on different features, fixes, etc. while isolating them from the main codebase. So a repo may have a master branch, and separate branches to work on different features.

Typically once the work is completed on a feature and it is recommended to delete the branch.

The Delete workflow:

Lets say you have a repo called as AwesomeRepo, and its hosted on Github, at a location such as https://github.com/my_username/AwesomeRepo.

Also lets assume it has the branches like: <br>master<br>feature/some-cool-new-stuff<br>fix/authentication<br>staging<br>

For consistency we will assume branch names are same on local as well as on the remote.

Now, lets say you are done with that fix for authentication and want to remove the branch fix/authentication.

When to Delete branches?

Normally in a contribution flow Branches are a great way to work on different features, fixes, etc. while isolating them from the main codebase. So a repo may have a master branch, and separate branches to work on different features.

Typically once the work is completed on a feature and it is recommended to delete the branch.

The Delete workflow:

Lets say you have a repo called as AwesomeRepo, and its hosted on Github, at a location such as https://github.com/my_username/AwesomeRepo.

Also lets assume it has the branches like: <br>master<br>feature/some-cool-new-stuff<br>fix/authentication<br>staging<br>

For consistency we will assume branch names are same on local as well as on the remote.

Now, lets say you are done with that fix for authentication and want to remove the branch fix/authentication.

Ruby

Ruby is a dynamic, object-oriented, reflective) programming language with a focus on simplicity and productivity. It has an elegant syntax that is natural to read and easy to write. It also has a dynamic type system and automatic memory management.

Known for its syntactic sugar, Ruby is made for developers happiness. It was created by a Japanese software engineer, Yukihiro Matsumoto in the early 1990s (also popularly known as Matz) as a simple general purpose scripting language for his day-to-day work. Combining elements of Perl, Smalltalk, and Scheme in a simple yet powerful syntax.

Ruby was conceived on February 24, 1993. In a 1999 post to the ruby-talk mailing list, Ruby author Yukihiro Matsumoto describes some of his early ideas about the language:

I was talking with my colleague about the possibility of an object-oriented scripting language. I knew Perl (Perl4, not Perl5), but I didn't like it really, because it had the smell of a toy language (it still has). The object-oriented language seemed very promising. I knew Python then. But I didn't like it, because I didn't think it was a true object-oriented language — OO features appeared to be add-on to the language. As a language maniac and OO fan for 15 years, I really wanted a genuine object-oriented, easy-to-use scripting language. I looked for but couldn't find one. So I decided to make it.

Like Perl, Ruby is good at text processing. Like Smalltalk, everything in Ruby is an object, and Ruby has blocks, iterators, meta-classes and other good stuff. You can use Ruby to write servers, experiment with prototypes, and for everyday programming tasks. As a fully-integrated object-oriented language, Ruby scales well.

By 2000, Ruby was more popular than Python in Japan; but as the Ruby on Rails web framework was created and released; it grew in leaps and bounds, well beyond Japan.

Today, Ruby on Rails is considered a solid web framework; and it has pioneered lot of great practices in web development.

When to Delete branches?

Normally in a contribution flow Branches are a great way to work on different features, fixes, etc. while isolating them from the main codebase. So a repo may have a master branch, and separate branches to work on different features.

Typically once the work is completed on a feature and it is recommended to delete the branch.

The Delete workflow:

Lets say you have a repo called as AwesomeRepo, and its hosted on Github, at a location such as https://github.com/my_username/AwesomeRepo.

Also lets assume it has the branches like: <br>master<br>feature/some-cool-new-stuff<br>fix/authentication<br>staging<br>

For consistency we will assume branch names are same on local as well as on the remote.

Now, lets say you are done with that fix for authentication and want to remove the branch fix/authentication.

When to Delete branches?

Normally in a contribution flow Branches are a great way to work on different features, fixes, etc. while isolating them from the main codebase. So a repo may have a master branch, and separate branches to work on different features.

Typically once the work is completed on a feature and it is recommended to delete the branch.

The Delete workflow:

Lets say you have a repo called as AwesomeRepo, and its hosted on Github, at a location such as https://github.com/my_username/AwesomeRepo.

Also lets assume it has the branches like: <br>master<br>feature/some-cool-new-stuff<br>fix/authentication<br>staging<br>

For consistency we will assume branch names are same on local as well as on the remote.

Now, lets say you are done with that fix for authentication and want to remove the branch fix/authentication.

Adding Snippets To Your Sublime Text Installation

If you are a user of sublime text (I hope you are, it kicks ass. You can get it here), then you may havealready noticed some of the tab completion capabilities. For example, when you are opening an html tag such as <p>, it automatically closesthe tag as soon as you type /. You can get similar functionality for pieces of code you end up re-writing over and over, and it's surprisinglyeasy!

Here's an example, which activates after typing div and then tab:

The Steps

Step 1.

Click Tools > New Snippet... in the navigation bar. This will open a snippet skeletton file which will look like this:

Creating a Project with Django

Now that we know how to create virtual environments and use pip, we can beginbuilding our project. In this article, we will create our first Django project,write tests, and start our development server.

Creating the Virtual Environment

First, let's create a new virtual environment for this project. (If you haven'talready, deactivate the previous virtualenv by typing deactivate in theterminal). For more info on virtual environments and how to use them, visitthis page.