More published code is better than less published code irrespective of quality, because it tells me that you're engaged and devoted to your craft, and it gives me a sense of what projects and technologies you're interested in and have been exposed to. Additionally, publishing code gives me a way to see your progression through the craft, and to get a sense of not only how developed you are as a programmer, but how you're growing.
A junior programmer who shows growth and improvement is a much better hire than a junior who is competent but shows no growth. When I hire people, I want to hire people who will grow into strong senior developers over their career, which means that I'm primarily looking for ability to learn and grow rather than a specific buzzword checklist. Hiring a junior comes with the expectation that I'm going to have to train and hand-hold them, but I want to hire a junior who will progress out of that stage, and will be able to start taking care of those things for new hires down the road.
Publishing code on Github doesn't mean that you're asking other people to use it; it just means you're publishing it. A Github profile on a resume is a +1 for me; a Github account with a lot of forks is another +1, an account with original code is yet another +1, and an account with original code that other people use is the big cherry on top. In all cases, though, I'd rather see an active account filled with "noobish" or "messy" code than an empty account.
