A developer's portfolio: what it's made of

What it actually is

A developer's portfolio isn't a pretty separate website. It's a body of evidence that you can do the work. Form is secondary; substance decides.

The minimum working set: two or three projects with live links, open code, and a clear statement of your role in each.

What it contains

Projects. The core. For each: what it is, why, what you did, which technologies, a working link, a link to the code.

A README. The first thing anyone reads. Without it, the code barely gets looked at.

Commit history. It says more about you than the description: it shows whether you worked steadily or assembled everything in one final night.

Confirmation of your part. In a team project it must be clear which part was yours. Best of all when it's confirmed by the person you worked with rather than by the CV's author.

Profile links. Public profiles with visible activity, contributions to other people's projects.

What gets looked at first

According to people who read CVs: they open the live link first. If it doesn't open or looks broken, they usually stop there.

Then the README. Then a quick glance at the structure of the code. Only if all that survives do they read the code closely.

The conclusion is simple: a working link and a clear description matter more than elegant code.

Do you need a separate portfolio site

Not necessarily. A tidy profile on a code hosting service with pinned projects does the job.

A separate site helps designers and front-end developers — there it's a work sample in itself. For everyone else it rarely adds anything but lost time.

Common mistakes

A list of fifteen repositories. Nobody works out which matter. Keep three and hide the rest.
Links that don't open. Check monthly: free hosts like to fall asleep.
No statement of role in team projects. "Participated in development" means nothing.
Empty repositories with a single file. Better hidden.

What strengthens it

The gap between "I did the backend" and the same sentence written by the person you worked with is enormous. The first reads as a claim, the second as testimony.

And when your commit history sits next to that description, nothing has to be taken on trust at all.