Thanks for taking the time to read my article! If you have any questions or ideas to share, please feel free to contact

In Python, we use parentheses in the class declaration to show an inheritance relationship. In the transportation example above, I’ve used Python’s syntax to tell the computer that both the car and the train inherit from the MyTransports class. Because of this, they automatically have the same constructor, which sets the color and brand attributes.

Once you include documentation to your classes and objects, you’ll get much more information about the methods created that will facilitate re-usability of the code and help other users to understand it. Remember that the docstring always has to be indented at the same level of the block it’s documenting.

git rebase is great because the resulting git history is a straight line. There’s no single commit that has more than one parent. However, after the rebase, commits “f1” and “f2” are no longer true preservations of the original “f1” and “f2” commits. Their commit ID will be different. Their content may be different. And as a result, you fall into the same issue which git filter-branch created. If you’re working with a shared remote repository and conducted the rebase locally. You’ll need to force push the rebased changes to the remote repository. A force push risks permanently removing valuable changes that may have been on the remote repository. Additionally, a force push destroys your collaborators’ ability to push/pull to/from that branch on the remote repository.

In an object-oriented language like python real-world concepts are represented by classes. Instances of classes are usually called objects. Such objects have attributes which are used to store information about them and we can make objects do work by calling their methods. The objective of this article was to give you a clear notion of how useful O.O.P. is for a programmer as it allows us to model real world concepts.

This is actually a really big deal for designers. Over the years we fell into a typical trap in computing — the more power we had (and used) the more we realised that it’s never enough.

Generally, teams relegate the use of git rebate to only occur during pull requests to the master branch. Thus, avoiding the potential for collaboration issues. However, I still prefer to never rewrite history.

When working with a team of developers, it is important for git to not get in the way of seamless collaboration. Generally speaking, behavior within git that re-writes history or alters the convention of how most people interact with git should be avoided. Git submodules alter the general git convention by causing changes to be tracked on multiple levels as opposed to just once for the entire project. git filter-branch and git rebase both re-write your git history. And we discussed that there are complications that arise when the git history is changed. In my opinion, git rebase has little advantage over git merge and should almost always be avoided. However, git filter-branch has its uses in dire situations. It’s an “Oh $#!