If You Call Out Bad Code, Make Sure It's Bad First
> Now, I’m all for bad projects and bad code being called out.<p>Bullshit, sorry.<p>Questions to ask yourself before "calling out bad code".<p>1. Does this code belong to someone on your team?<p>2. Does your code rely on this code?<p>3. Does the code represent a risk to you or your business in some way?<p>4. Do you have the direct contact info for the developer so you can appropriately, discretely and professionally inform them about their code?<p>Github == "Developer Playground/Experimentation Lab".<p>Why in the hell should I have to feel that every piece of code I put up there 'must' adhere to 'your' standards or anyone else's?<p>How can we as a development community rationally expect to grow the open source ecosystem and encourage people with this type of snobbery?