Development cycle vs publishing your code on Github
Many recruiters and various people in hiring positions look for code on Github to evaluate if a candidate is advanced enough as if this somehow means they are the person suitable for the job. Let alone that the side projects usually come from motivations unrelated to employment, the likelihood that the person has written something that relates to what the company is hiring for is very small. The REAL issue though, is that the development cycle when you do actual work in production is not at all conducive to publishing code online for everyone to see. Key issue - environment variables. Inevitably, when you are testing whether your bash script works you will hard-code paths into it, which relates to your system and your web domains alone. While the practice is frowned-upon, this is how it works. You use /var/www/mydomain.com/html before you turn it into a shell variable. This means that you not only need to care about your code being manageable, you need to "beautify" you code...