Step 1. Find a real user
At least one, even if it's you. Ask yourself: what would it take for you to actually use this?
Nobody needs a practice shop. A personal expense tracker, a reminder for expiring subscriptions, a search over your own notes — those are usable. Often changing the subject while keeping the code is enough.
The moment there's a real user, real problems appear: the input is awkward, data gets lost, an export is needed. Those problems are exactly what makes a project real.
Step 2. Deploy it
A project you can't open behind a link half doesn't exist. Nobody will clone a repository to look at your work.
Deploy it on any free host. It's one evening, and the difference is enormous: the link goes on your CV, and people follow it.
Step 3. Write the description
The README is the first thing anyone reads. It needs four things:
- What this is and who it's for, one plain paragraph.
- How to run it: commands that genuinely work.
- What's inside: technologies and why you chose them.
- What's next: what's missing, what you plan.
That last point is underrated, and it shows you can see the weak spots in your own work. That counts.
Step 4. Sort out the change history
If all the code arrived in two commits, it shows. From here on, work normally: small changes with clear messages. In a month the history will read like work rather than a submission.
There's no need to rewrite the past. Starting to do it properly from now on is enough.
Step 5. Bring somebody in
The strongest step and the one most often skipped. Invite one more person and hand them part of the work.
It changes the project qualitatively: division of tasks, discussion of each other's code, the need to negotiate. That's the experience almost everyone who studied alone lacks, and it's what interviews ask about.
You also gain something a solo project can't give: a person who can state in their own words what you did. That kind of confirmation carries more weight than the tidiest line on a CV — especially with your change history visible next to it.
Открытые роли по теме статьи
Читать полезно, а делать — ещё полезнее. В эти команды можно написать прямо сейчас:
- iOS-разработчик — MAIBO - MedTech-пилот для клиник
- Контент-маркетолог / комьюнити — CohortX — платформа командных пет-проектовмаркетингtelegramseoконтент
Похожие статьи
- Study Tools Season: two weeks, a team, and a finished projectCohortX launches its first season: September 7–21, teams of 2–4 build one study tool each — from schedules to progress trackers. How to join and what it adds to your portfolio.
- Сезон инструментов для учёбы: две недели, команда и законченный проектCohortX запускает первый сезон: с 7 по 21 сентября команды по 2–4 человека делают по одному инструменту для учёбы — от расписания до трекера прогресса. Как участвовать и что это даёт портфолио.
- A portfolio without commercial experience: what belongs in itHow many projects you need, which ones carry weight, how to present a repository, and what to do with coursework.