Understand the pros and cons of using GitHub
As a developer, you may have heard of GitHub, or you may have used it yourself.
GitHub offers a Git repository service, which is web based and allows you to use Git’s source-code management functionality, along with its own features.
Many people in the creative and technical developer circles rave on about GitHub. How good is it really and is it worth the trouble learning Git to use it? There are many benefits to using GitHub, however there are also are some noted disadvantages which we’ll discuss here.
So let’s begin to better understand the pros and cons to using GitHub:
- GitHub is a very versatile tool to use. It’s ideal for working on projects of any size and it’s a great tool for web work flows. Firstly you can use it for publishing your work, as a versioning control system and as a collaborative tool.
- With GitHub you can archive your projects and share them with your peers for either inspiration or for them to collaborate on. The beauty of it is that you can have more than one person collaborate remotely on a project, so you’re all on the same page, so to speak.
- It’s ideal for creating a backup of your work instead on saving the code on a desktop or on a corporate server.
- It is also beneficial to use if you’re learning Git. One way to look at it is seeing Git as a preventative maintenance process, where you get into the flow of doing reverts, commits, pulling, pushing, and so forth, as needed. It can save you a lot of hassle if a problem occurs, or if you need to revert code of any sort. One of the best features is being able to track mistakes, and it’s definitely made easier by using GitHub. Bugs can be opened, and thanks to GitHub, you can add commits to these and associate it with the problem.
- With GitHub pages, you can get started quickly without worrying about setting up hosting or DNS.
- If you’re new to GitHub, one of the challenges often talked about is getting to grips with the mental model, which eases with practice and time.
- It may not be the best tool for capturing the creative process or for recording ideas. A good tool for this particular function would be LayerVault or something similar to it. We’d say Git is very good for tracking code, however it’s not the best for tracking design. It can seem a little bit of a grey area when designs are needed to be translated into code or for when you need to export designs to a production setting.
- It depends on the designer, however, some find the GUI a little confusing to use and opt to use its CLI instead. Some developers learnt Git by mostly using commands, which explains why the GUI isn’t always liked by them. With a little practice, the commands are not too difficult to learn. However using Commands everyday can be awkward, especially when tracking project history or resolving conflicts. Then, there are others who’ve preferred the GUI instead of commands, as the visual representation of previous commits, modified files and diffs can make better sense. As mentioned previously, it can take some getting used to.
- It costs to have a versioning repository on GitHub, however it is worth the investment if you’re working professionally.
Overall, it’s always good to use a versioning control system. It’s definitely worth the effort, time and investment as it can give you much more flexibility and peace of mind for any project.
Git overall, is useful for anyone who codes, giving any developer or coder plenty of value to not take notice of it. And what better way than to use a platform such as GitHub. The price plans are very reasonable, even for private use with 5 repositories at $7 a month with unlimited collaborators or for corporations $25 a month for10 repositories.
Now you have a clearer overview on the pros and cons of using GitHub, we hope that article has served you well in understanding its potential.