I'm on a hiring panel and often look at github accounts for potential candidates. So to answer your question "add a repository" or "create a new project". Those are two different things. A repository is essentially your code, it's a place to store (and version) your code. In github speak, a project is how you track the work associated with your repo. But the repo is actual code itself, if that makes sense. Rather than simply using github as a way to upload source code, I would encourage you to learn git and specifically how to make regular commits as part of your workflow. Version control is a key tool for software developers and will provide you with a lot of value, even in school. If you're not too familiar with git, please see the free code school course on git https://www.codeschool.com/courses/try-git Things that I look for when looking at git repos: Is there a readme page that explains the purpose of the repo. This should also include documentation on how to run the code. Are there unit tests (or any tests) as part of the repo. How many commits are made on the repo? Github exposes all the git commit history. It's nice to be look at a project and see how it has grown over time. Rather than a single commit with "here's the code". I look at commit messages. Are they useful? Do they provide value and express the reason for the change or is something like "changed shit" (which is a horrible commit message btw). Groupings . A repo should represent a single project, and sometimes I see a single repo with just hundreds of random code files that are in no way related. Most importantly I pick a few random files and look at the code, is it following common standards. Does it follow conventions and styles? How easy is it to read? Are there comments? Are there too many comments? Basically looking for items from the book code complete (which is a great book btw). When it comes to code, some things to keep in mind: Don't have long blocks of commented out code. This is just a waste of space and adds visual bloat. If you're worried about losing that code, it won't be lost if you use git correctly and have several commits. you can always go back in git. Variable names. Are the names meaningful and express intent or is it something like "int something1; int something2" which provides me no context. Duplication. Is there a lot of duplication in the code? Could it be rewritten in a way to follow the DRY principle(don't repeat yourself.) Comments that state the obvious. for example //returns the count int getCount(){ return _counter; } That comment is useless because it's redundant. I hope this was helpful. Good luck! More on reddit.com

I don’t mean to be blunt, but the scope of this question is too broad to provide you useful information (IMO). So my suggestion is: Do some self guided research on this topic Come back with more specific questions I think you’ll get more useful replies if you spend 0.5-1 day on step one. More on reddit.com