| No. At a different level from the other "no"s. You are a good developer if you make stuff that helps people. Not if you have an impressive résumé, not if you make a lot of money. Not even if your stuff is really technically impressive or shows off IQ or promise. Really, that's important. There's a lot on this site about being the cleverest, the fastest, knowing more comp sci than the next person or handling trickier interviews or proving there's something wrong with some other ecosystem, program, language, etc. Sometimes I'm not sure everyone feels they have a job to do that can improve people's lives. Whether sideprojects can sometimes help you reach career goals is a more appropriate question. For applicants I think there's an initial threshold of whether they can ship nontrivial stuff. They can demonstrate it with their past jobs or by actually building stuff. A sideproject could certainly help you get hired if you have no experience and the credentials aren't getting you there; it might be smart to do if you're having trouble finding right work out of college, say. Likewise, it might help you show you have potential in a radically different specialty that your past experience has no bearing on (e.g., you used to write Ruby on Rails but want start to writing code for microcontrollers). And if someone has unrealistic expectations about how much of a rockstar you need to be, maybe you don't want to work for them. If a potential employer wants you to have a github account that shows you spend all weekend every weekend hacking, maybe you dodged a bullet when they didn't hire you. I say this having just taken a bunch of time to build a side project. It was fun and stuff (building from scratch instead of tweaking a giant codebase! learning golang! making things go fast!) but there's no possibility in my mind it makes me "better" or I'd be "bad" had I not done it. |