What a portfolio is actually for

A portfolio is not a gallery. It exists to answer one question in the reader's mind: can this person do the thing, without me having to supervise every step?

Everything follows from that.

Why certificates are not enough. A certificate says you attended. A working project says you finished something. In this field, finishing is the rare part — the internet is full of people who completed a tutorial and nothing else. Anyone hiring knows this, which is why they ask what you have built.

Who is reading, and how long for. Assume ninety seconds, on a phone, by someone with twenty other applications. They are scanning for: is there something real here, does it relate to what I need, and can I see it working. If they must download something, install something, or read four paragraphs before understanding what it is, they are gone.

Three projects beat twelve. A long list of half-finished exercises signals someone who starts things. Three complete pieces, each solving a recognisable problem, signals someone who finishes them. Remove the weakest one — it is what they will remember.

Tutorial projects are nearly worthless as evidence, and this is the hardest thing for a beginner to hear. If ten thousand people built the same to-do app from the same video, it proves you can follow along. Change it substantially, or build something for a real situation you actually know.

The strongest possible portfolio item for this pathway is something a real person or business actually uses — even a small one, even unpaid, even your family's shop. One working automation that saves someone twenty minutes a day is worth more than five impressive-looking demos, because it proves you can operate in reality, where the data is messy and the requirements change.