Programming Technology

Your GitHub is read before your CV, and usually for about ninety seconds

Nobody reads your code first. They read how you work — and four things visible without opening a single file decide whether the code gets read at all.

Your GitHub is read before your CV, and usually for about ninety seconds

If you put a GitHub link on your CV, it gets opened before the CV is finished. What happens in the next minute and a half is decided by four things, none of which require opening a source file.

1. Is there a README, and does it say what the thing is

A repository with no README is a repository nobody can evaluate. The reviewer does not know what it does, who it is for, or whether it runs.

Six short lines will do it, and part one sets out which six. Writing them is the highest-value ten minutes in the whole exercise, because the README is the only file that everyone who opens the repository actually reads.

2. Is your .env in the repository

This is the one that ends the review immediately, and it is common.

A committed .env means your database password and application key are published. Worse, deleting the file in a later commit does not remove it — it stays in the history, readable by anyone who knows how to look.

Check now. If it is there, treat those credentials as compromised and change them, then clean the history or start the repository again. Do not simply delete the file and hope.

A committed .env stays in history
Deleting the file later does not remove it. Change the credentials, then clean the history. Graphic: Tech BD.

3. Is vendor/ or node_modules/ committed

Hundreds of megabytes of other people's code in your repository tells a reviewer you have not used .gitignore, which means you have not worked on a team.

Neither folder belongs in version control. Both are rebuilt from composer.json and package.json, which is the entire reason those files exist.

4. What your commit messages say

Open the commit list. Forty entries reading "update", "fix", "update again" describe someone who saves work. Messages like "validate the upload size before storing" describe someone who finishes a thought before committing it.

Nobody expects perfect history from a junior. The reviewer is checking whether a future colleague could work out why you changed something, six months from now, without asking you.

What is not worth optimising

Three things absorb a lot of effort for almost no return, so it is worth naming them before you spend a weekend on any of them.

The green contribution graph is widely misunderstood. Nobody serious is counting your daily squares, and a wall of green from automated commits is more suspicious than an honest gap.

Pinned repositories do matter: put the finished, deployed project first. The reviewer reads top-left and often no further.

A profile README is optional and makes almost no difference. Spend the time on the project README instead.

The series in one line

Build one project that goes all the way (part one). Be able to say why you made each choice (part two). Put it on a real domain (part three). Make the repository readable in ninety seconds (part four).

None of this is about being a better programmer than the other applicants. It is about being the one whose work can actually be inspected — which, when an employer is weighing three or four months of training, is most of the decision.

Source: Tech BD

Written by

Tech BD

Tech BD is an independent technology publication based in Dhaka, published in English and Bangla. Articles appear under the masthead rather than under individual bylines; corrections and source questions reach the editor at info@tech-bd.com.