The Relevance of GitHub for Professional Coders
Does a lack of a GitHub account mean a coder is less competent? In this article, we explore the role of GitHub in the professional world, the importance of open source projects, and the diversity of coding experiences. Whether you are a seasoned developer or just starting your journey, the value of GitHub can often be misunderstood.
Understanding the GitHub Ecosystem
GitHub has become a cornerstone for many developers, acting as a platform to share code, manage projects, and collaborate with others. However, not all professional coders use GitHub, and there are valid reasons for this. For those with extensive experience or those working on proprietary software, the need for a GitHub account might not exist. Let us delve into the nuances of GitHub and its impact on professional development.
Is GitHub the Only Option?
Many developers mistakenly believe that GitHub is the only platform for sharing code. This is far from the truth. There are numerous other platforms available, such as GitLab, Bitbucket, and others, each with its own features and advantages. If a seasoned coder does not use any of these platforms, it does not necessarily indicate lack of competence. The decision to use a particular platform often depends on the specific needs and requirements of the project.
A Personal Perspective on GitHub
Recently, a software developer shared his experience of being a coder without a GitHub account. This coder works for a company that uses proprietary languages, and it does not require him to share his code publicly. His professional work involves peer reviews and collaboration within the company. He also maintains a busy schedule as a software developer, support associate, and play area monitor. His free time is spent on hobbies that are not related to coding. This situation is not unique, and many developers thrive in environments where open source projects are not required. It is important to recognize that not all developers engage in hobby projects or participate in open source initiatives, and this should not be a determining factor in evaluating their competence.
The Implications of Not Using GitHub
Do recruiters and business people unfairly discriminate against developers who do not work on hobby projects or stay active on GitHub? The answer is a nuanced one. While GitHub can be a valuable tool for sharing and discovering code, it is not a requirement for professional competence. In fact, many developers have successful careers without using GitHub, and their coding skills are recognized through other means. It is unfair to assume that someone is less competent simply because they do not have a GitHub account or do not participate in open source projects.
The Importance of Real-World Experience vs. Open Source Projects
Many seasoned developers have learned their craft through hands-on experience rather than through open source projects. They might have developed proprietary software for enterprises using languages like J2EE or .NET. These developers often focus on their professional work and contribute to the success of their companies. While it is beneficial for developers to have open source projects under their belt, it is unfair to judge their competence based solely on their GitHub activity. Just as one would not doubt the competence of an accountant, lawyer, or doctor because they do not engage in their respective hobbies, it is unfair to doubt a developer's competence based on their GitHub activity.
Furthermore, many developers grew up before the GitHub hype. During their formative years, they might have developed hobby projects but kept the code to themselves. When sourceforge became popular, some projects did find their way to it, but not all. Developers today often keep their hobby projects privately and only make them public when it makes sense. This practice is not indicative of a lack of competence or unwillingness to contribute to the community.
Conclusion
In conclusion, the decision to use GitHub or other platforms should not be the sole determinant of a coder's competence. Professional developers often have valid reasons for not using GitHub, and their skills are not diminished by their lack of a GitHub account. It is essential to recognize and value a diverse range of experiences and backgrounds in the coding community. Let us promote a more inclusive and understanding approach to professional development and career evaluation, free from biases and assumptions based on a single platform.