>Most GitHub Projects Aren't Impressive So make an impressive one. My team lead would sometimes ask me to help evaluate potential candidates and sometimes we

>Most GitHub Projects Aren't Impressive So make an impressive one. My team lead would sometimes ask me to help evaluate potential candidates and sometimes we looked at GitHub profiles if one was supplied. No problem if not, but if so then it's a data point. The claim above from the article is true. Mostly nothing is actually impressive and if you're not careful it's easy to have something count against you. It's actually a bit of a trap. As a result of that I decided to make all 50 public repos I had private and instead just work on a single public repo of decent depth/quality. What I wound up doing is create a small web app in a domain I would never be interested in trying to turn it into a commercial product, then I use it as not a single project, but a series of inter-related projects that build on each other. Mostly it's a playground for me to learn new things and explore ideas. So I first did an API. Then once I had an API I took the opportunity to learn a new front end tech and made a front end with it. Now I'm working my way through learning IaC with it. After that I'm gonna use it to learn serverless. Each additional project with it makes it more valuable to me. More valuable in the sense that each project completed increases my motivation to do the next one because it becomes a more fully fleshed out piece of software and feels more "worth it". I haven't switched employers since I started it about a year ago, but I think it'll definitely help with positioning. As it is it helps me with my career anyways as I have a semi-realistic environment in which to try things out to evaluate their pros and cons.