I recently watched a video where someone was criticized for not being a ‘legitimate programmer’ because they didn’t have any public code repositories online. This got me thinking about whether this expectation is fair.
Why should software developers be required to showcase personal projects or contribute to open source work during their free time? We don’t ask plumbers to demonstrate their pipe fitting skills as a hobby, and we don’t expect accountants to do bookkeeping for fun on weekends.
It seems like there’s this weird culture in programming where you’re expected to code constantly, even outside of work hours. Is this really necessary to prove your skills as a developer? What are your thoughts on this expectation?
this whole thing’s pretty toxic tbh. sure, having a github can help, but saying you’re not a ‘real programmer’ without one is just gatekeeping bs. tons of devs work on internal projects they can’t share publicly - that’s completely valid work too.
It’s not necessarily about coding in your free time; rather, it’s about demonstrating your skills to potential employers. A public repository serves as a portfolio for many developers, especially since corporate work often remains confidential due to NDAs. It showcases your ability to write code, organize projects, and document your work effectively. The criticism you’ve encountered is indeed harsh. Many talented programmers focus on proprietary projects which limits what they can share. The industry should recognize that contributions on platforms like GitHub aren’t the sole measure of a developer’s capabilities, particularly considering the diverse responsibilities many developers juggle.
The expectation for programmers to maintain public code repositories stems from the necessity of illustrating one’s coding abilities. Unlike fields where formal qualifications often take precedence, programming requires tangible evidence of skill through code quality and problem-solving capabilities. Hiring managers prefer this transparency because poor coding can lead to significant setbacks for teams. Public repositories reflect an individual’s coding standards and commitment to their profession. However, this norm can be unjust, benefitting those who have the time to engage in open-source projects while potentially sidelining capable developers who juggle demanding jobs and personal responsibilities.
This topic was automatically closed 4 days after the last reply. New replies are no longer allowed.