What makes a project portfolio-worthy (and what doesn't)

Not every finished project is portfolio-worthy, and not every portfolio-worthy project needs to be complicated. The difference isn't scale — it's whether the project gives you something specific to say when someone asks "walk me through this."

The filter: can you answer these three questions?

1. What decision did you make that a tutorial wouldn't have made for you? A todo app built by following a video, exactly as shown, teaches you the syntax but gives you nothing to talk about — every decision was already made by the instructor. A project earns its place in a portfolio the moment it required you to choose between two real options (which data structure, which library, how to handle a specific edge case) and you can explain why.
2. What's the one part you'd be nervous to explain in detail? If the honest answer is "there isn't one, it's all pretty simple," the project is too small to demonstrate much — not disqualifying, but know that going in. If the honest answer is "the concurrency handling" or "how I structured the database schema," that's your interview story, and it means the project is doing real work.
3. Is it actually finished, or just abandoned in a working state? A project with a clear stopping point — a README, a working demo, a specific set of features that are done — reads completely differently from an open-ended repo that trails off. "Finished" doesn't mean "feature-complete forever," it means you made a deliberate call about scope and hit it.

What doesn't matter as much as people think

Framework choice, project "impressiveness," and lines of code are all weak signals on their own. A small project you can discuss in real depth beats a large one you can only describe in generalities — an interviewer's follow-up questions will find the difference within thirty seconds either way.

Using this filter

Before starting (or before adding something to your portfolio that you already built), run it through these three questions honestly. If you can't answer at least the first two with something specific, either the project needs another pass, or it's better as a learning exercise than a portfolio piece — and that's a fine thing for a project to be, as long as you're not presenting it as more than it is.