A portfolio serves to help answer the two important questions employers need to know, "Will you do the job well?" and "Will you fit in?"
A good portfolio can demonstrate it by showing you have actually made good games.
Anything that suggests you will not do the job well or will not fit in might count against you. Bad source code, bad coding habits, bugs in playable demos, these could all discourage an employer from considering you. That is why everything in a portfolio should be your best work. If you have a hard time putting that together, it might be better for you NOT to have a portfolio. Unlike artists and animators, programmers can get jobs in the industry fairly easily without a portfolio. Generally the employer will give you coding tests and also ask a lot of tough questions that can weed out non-programmers handily.
As for your site specifically, I don't see anything I would hold against you as an entry level worker. It shows you care about creating games and that you have built a few small ones. The source code is far from perfect, but about what I would expect at an entry level. I would still give you programming tests and technical interviews, but what is up there is satisfactory. I would prefer to see more source code and documented links to that code, but wouldn't fight against what you posted there; it has some source, links to some executables (which I didn't run, but others might), both of which are useful in assessing your current abilities.
Edited by frob, 10 May 2014 - 11:04 PM.
Moving to job advice forum.