A reader message landed in my inbox this weekend.
I have a bunch of projects on GitHub. Is that my portfolio?
Short answer: no.
A GitHub is a repository. A portfolio is a story.
Two different objects. Two different audiences. Two different jobs.
GitHub is for the person who wants to read your code. That’s a tiny audience. Usually another engineer. Usually already inside your team.
A portfolio is for the person who doesn’t want to read your code.
And that’s the audience that actually decides whether you get hired, promoted, or brought into a room. Hiring managers. Product leads. Recruiters. Clients.
They don’t open notebooks. They don’t scroll commits.
They look for three things, in this order:
What problem did you solve
What decision did it change
What would you do differently now
None of that lives on GitHub.
Your GitHub has the raw material. A portfolio has the argument.
The gap between “I built things” and “I can show you what they mean” is the gap between a career that stalls and one that compounds.
Most data people are stuck on the wrong side of it.
Not because they haven’t done the work. Because they never translated it.
Next week I’ll break down why most data portfolios still fail the moment they land in front of a hiring manager. And what the ones that actually convert do differently.
For today, open your GitHub.
Pick one project.
Write two sentences about what decision it would have changed if the results had gone the other way.
That’s the seed of a portfolio.
Code proves you did the work. A portfolio proves you understood it.
— Josep
Are you still here? 🧐
👉🏻 I want this newsletter to be useful, so please let me know your feedback!
Before you go, tap the 💚 and the restack buttons at the bottom of this email to show your support, it really helps and means a lot!
What's one project sitting on your GitHub right now that deserves a portfolio page? Reply and tell me the one sentence you'd use to open it. 👇🏻