A GitHub portfolio for TCAS is a public folder of a student's code with a visible history, plus write-ups explaining what each project does, what went wrong, and how it was fixed — far stronger evidence than certificates alone.
What is GitHub, and why should a student have one?
GitHub is a public code repository that records every change, like a logbook of the whole process rather than just the finished result. A student with their own GitHub shows they wrote real, sustained code — which matters more than ever now that AI can produce code on demand.
Can GitHub actually be used for TCAS?
Yes, especially in the portfolio round (Round 1), where many computer-related programmes accept links to work. A GitHub link a reviewer can click and inspect carries far more weight than a description on paper, because it can be checked immediately rather than taken on trust.
Getting started with GitHub in an hour
- Create an account. GitHub's minimum age is 13; if your child is younger, a parent should register and manage the account.
- Create the first repository. Upload the code for one finished project — it does not need to be perfect.
- Write a README in Thai and English. Briefly explain what it does, why it was built, and what problems came up and how they were solved.
- Add a screenshot or a working link. Reviewers have only a few minutes per applicant; visuals and live links communicate faster than raw code.
- Link the GitHub profile inside the TCAS portfolio document.
What reviewers actually want to see
Reviewers are not looking for the biggest project. They are looking for work that was finished and can be explained. One small site that genuinely works is worth more than ten large, abandoned ones.
A profile with three finished projects and a clear story behind each beats one with twenty unfinished projects every time.
At our school, students taking the Junior AI-Assisted Developer course build a web shop from start to finish — an ideal first GitHub project. For a focus on websites specifically, see our web development course.
Common mistakes in student portfolios
The mistake I see most often is uploading code entirely written by AI that the student cannot explain. When an interviewer asks how a piece of code works, the student cannot answer — which costs more than having no project at all. Other common gaps: no README, and no dates showing progress over time.
Read more on building a strong portfolio at building a coding portfolio from secondary school, and see real examples on the student project page. If you are still deciding which field to pursue, computer engineering vs computer science vs IT may help.
Frequently asked questions
My child is under 13 and cannot register for GitHub alone — what do we do?
A parent should register and manage the account, per GitHub's age terms. The child can still upload code and write READMEs as normal.
Can I include code that AI helped write?
Yes, as long as your child understands and can explain every line. Do not upload code AI wrote entirely, since your child will not be able to answer a reviewer's questions about it.
How many projects are enough for a portfolio?
Three finished projects with a good account of what happened outweigh ten abandoned ones. Quality matters far more than quantity.
