The Registrar in Your Desk Drawer: Keeping a Transcript for Projects That Never Made It to GitHub

Somewhere on your laptop right now, there's a folder called test2_FINAL that contains three weeks of genuine learning. It never made it to GitHub. It has no commit history anyone can see, no green squares, no stars. By the traditional measures of the self-taught developer, it doesn't exist.

But you know it does. You wrestled a dependency conflict for a full Saturday. You finally understood why your API calls were failing. You learned something, and then the evidence evaporated.

Universities solved this problem a long time ago with a boring little document called a transcript. Every course, every grade, every credit — recorded by an office whose entire job is remembering what you did. When you teach yourself, you're also the registrar. Most people just never set up the office.

The Problem With Only Counting What's Public

GitHub is a great portfolio and a terrible transcript. It only shows shipped, public, presentable work — which is maybe 20% of what you've actually done. The other 80% looks like:

• The scraping script you built, broke, and rebuilt three times
• The tutorial project you finished and then modified until it stopped resembling the tutorial
• The database migration that taught you more about SQL than any course

None of that shows up in a recruiter's search. Worse, you forget it. Six months later, when an interviewer asks "so what have you built?", your brain blanks and you mumble about the one repo you polished.

Building Your Private Transcript

The fix is a single, low-friction document. A note app, a markdown file, a spreadsheet — whatever you'll actually open. Every time you finish something (or deliberately abandon it), add an entry with four fields:

1. Date. Just like a real transcript. Dates turn vague memories into a timeline, and timelines show momentum.

2. What it was. One or two sentences, plain language. "Built a CLI tool that renames photo files by date taken." No hype needed.

3. What broke and what you did about it. This is the field nobody else's transcript has, and it's the most valuable one. "Hit a rate limit, added exponential backoff" reads like experience — because it is.

4. Skill tags. Python, APIs, error handling, whatever applies. This becomes searchable later.

Ten minutes a week, tops. The barrier to entry for record-keeping should be embarrassingly low, or you won't keep it up.

Failures Belong on the Transcript Too

Here's where this differs from a portfolio. A portfolio is marketing. A transcript is a record — and records include the W's and the incompletes.

Log the project you abandoned, with a one-line autopsy: "Stopped because I picked a stack too far over my head; learned that I should prototype in something familiar first." That sentence is worth more in an interview than another polished to-do app, because it demonstrates judgment — the thing employers say they can't verify in self-taught candidates.

When someone asks about a gap or a struggle, you won't be scrambling. You'll flip to the entry.

Turning the Transcript Into Interview Ammunition

After a few months, you'll have something no bootcamp certificate can match: a dated, specific account of your own learning. Before any interview, spend twenty minutes rereading it and pull out three entries that map to the job posting. Each one gives you a story with a beginning (the problem), a middle (what broke), and an end (what you did).

That's the exact structure of a good behavioral interview answer, and you didn't have to invent it under pressure — you wrote it down when it happened.

Some people go further and keep the transcript in a public repo or a personal site's /now page. That's optional. The private version does 90% of the work, because the point isn't an audience. The point is that when nobody else is keeping score, you still have a scorekeeper.

Start Tonight

Open a blank note. Title it "Transcript." Write today's date and the last thing you finished or abandoned — even if it was just getting your dev environment working after a laptop crash. That counts. Especially that.

Degrees come with registrars. You came with a desk drawer. Use it.