How Should a Junior Developer in Spain Separate Bootcamp Tutorials from Real Projects?

A junior developer should lead with independent or team projects they can explain, label guided tutorial work clearly, and separate deployed applications from exercises that exist only as repositories.

A reviewer does not expect years of products from a bootcamp graduate. They do need to understand which decisions were yours, what still works, and whether a familiar clone followed a course. Honest structure makes smaller projects more credible.

Which bootcamp projects belong in the portfolio?

Include projects that demonstrate a relevant skill and that you can explain in detail, even when they began as coursework.

Prefer a small maintained application with your own decisions over several untouched tutorial clones. For team work, state your contribution and do not claim the entire system.

Remove secrets, personal data, broken deployments, and placeholder content before linking. If the code cannot be public, describe only what you are authorised to share.

What is the quick way to structure the junior portfolio with IndieShow?

The quick way is to create an IndieShow page and group deployed work, completed exercises, active learning projects, and retired attempts by status.

Use Shipped or Built for finished work, Building or Working on for genuine current development, and Archived for experiments you keep as history. Add a precise tag and one destination per project.

Order entries by relevance to the role, not by course module number, and use the live preview to ensure the first cards make sense without extra explanation.

Build your IndieShow pageClaim a handle, organise the projects in the editor, and review the $15 one-year and $30 lifetime publishing options in the dashboard.

How do you label a tutorial clone honestly?

Say that it was guided work, name the part you changed, and avoid presenting the original product concept as your invention.

A good description can explain that you implemented authentication, redesigned the data model, or added accessibility after following a base tutorial. If you made no independent changes, the exercise may belong in a learning log rather than the main portfolio.

Do not add fictional users, revenue, performance, or production usage to make the project sound larger.

Should the project link to a live demo or GitHub?

Link to a working demo when the user experience matters and to GitHub when the code and explanation provide stronger evidence.

Test the destination on mobile and without your own account. A demo with a broken backend or exposed seed credentials is not better than a clear repository with setup instructions.

The related IndieShow guides cover CV links and ordering multiple side projects.

Continue with: choosing one developer CV link · showing several projects on one page

How does IndieShow help the junior portfolio grow after the bootcamp?

IndieShow keeps the same personal URL while you replace exercises with stronger work, update descriptions, and move old projects to Archived.

That means the link on a CV can improve without rebuilding a custom site. The original demos and repositories remain the evidence, while the page records which work represents you today.

Close with the project you can discuss most confidently, your exact contribution, and a destination that works. Honest depth beats a long list of unexplained clones.