Publishing code in order to improve my chances to be admitted to a CS graduate school I am 32 years old now and I want to apply for a degree in computer sciences at a European university. I am afraid they could consider me to be too old. That's why I want to show them somehow part of my code and improve that way my chances to be admitted at my age. 

I thought about uploading a video in Youtube showing how my program runs and publishing the code of the program in other place, and then putting the links inside my CV. I am not sure how to do all this. My code is an unfinished emulator. It is about 20 000 lines of pure ASM and it hard to read. I feel that I need a way to prove that the video shows a real existing program and not only fake animation I may have done.


First, I wish to know if it is good to put the links to my code and videos inside the CV.
Second, I would like to know the best site (and simplest to use) to publish my code. It would be not lucrative at all for somebody to steal my code. Still I think it would be painful to find out some day that someone copied and pasted chunks of my code and said that he made it. I need a basic protection against plagiarism provided by the site. Maybe based on the date I posted the code.
Third, I am very worried about critics. This is 20 000 of ASM code(only part of the nearly 50 000 lines long project). It is messy! It looks really ugly. It is cool and highly optimized but I know there is always place for more optimization. I love it, it uses lot of SMC and code reusing. I love it but always there are people who could say it is junk.
Fourth, it is not finished. It works perfectly, but part of the OP-codes are not coded yet. I coded more of them, the ones I think would be used more frequently.


Given a situation like this, what would be the best way to proceed with sharing code to help boost chance of admission?
It sounds like you have a portfolio that should be a part of your application to university or a job or anything. Furthermore you're saying that the working product is a better testament to your skill than the code itself. This is also fine.

The only concern I see is how much work you will require on the reader of your application. If you link to a YouTube video, also include screenshots. If you link to a GitHub profile, consider writing up some basic statistics on the activity or health of your activity there.

Regarding where to publish code, don't overthink this. Github is popular, but a Dropbox file, a Google Doc, a file sharing service, or anywhere else you can post a file will do.

I do not know the proper channel to submit a portfolio or the proper format. This situation is probably documented in the application instructions however, so you should be able to find info there, or reach out to a recruitment officer for how to proceed.

EDIT regarding where to post - actually a .zip file or similar may be problematic since they tend to look like viruses to people, who don't want to open them. Github or a competitor may be the best choice since the source code is browsable in their web UI. It is best practice to include a software license whenever you publish (literally "make public") code, even if you think it is unusable. I think the MIT and Apache licenses both amount to (IANAL) "do whatever you want with it, just don't sue me."