Theory
The code nobody could see
Anvi applies for an off-campus engineering fellowship. Her resume says: 'Skilled at designing efficient MySQL schemas and responsive frontends.' The hiring manager is reading fifty resumes that all say nearly the same thing. Curious but unconvinced, they look for a link to actually see her work, and find nothing. Anvi's projects live only on her own laptop, tucked away in her Surat lab logbooks. When anyone can type the same keywords onto a document, code that nobody can open counts, to a recruiter, as code that does not exist.
Theory
The menu photo versus the actual dish
A resume is like the photo and description on a menu: it tells the reader what you can make, but they cannot taste anything. A portfolio website is like handing them the actual dish. When you send a recruiter your portfolio link, they can click your projects, open the app, poke at the buttons, and watch your work run for real. Description gets you noticed; letting them try it for themselves is what earns their trust.
Theory
The idea, plainly
A portfolio is a simple website that gathers your best projects, skills, and background in one place a recruiter can visit. For a computing student, it does what a resume cannot: instead of just claiming you can build things, it links straight to your live projects, your GitHub code, your LinkedIn, and even a professor's reference, all from one clean page they can explore in a couple of minutes.
At a glance
Turning flat claims into things a recruiter can see and check.
| Part of your profile | What a resume can only say | What a live portfolio can show |
|---|---|---|
| Proving a project | A one-line row: 'Built a web app for an e-commerce shop.' | A project card with a link to the working app and a tidy, documented GitHub repo. |
| Showing your skills | A plain list: 'Java, React, SQL'. | Small project blocks where the reader can actually see your code in action. |
| Backing up your claims | 'Excellent worker with a strong learning mindset.' | A real quote from your professor, linked to their signed recommendation letter. |
Follow along
How Anvi builds and publishes her portfolio
- Pick your best work Anvi goes through her Semester 2 database and web lab projects, picks her top 3, and tidies up each repo with a clear README explaining what it does.
- Lay out one clean page She builds a simple, responsive single page with four sections: a short intro, her tech skills, her project cards, and a way to contact her.
- Put it online She pushes the site to GitHub and connects it to a free hosting service, giving her a real, public link she can put on every application.
Quiz
Anvi is choosing fonts, animations, and colours for her portfolio site. Which approach works best with tech recruiters?
- A clean, high-contrast layout that loads fast, with a few subtle hover effects that lead the eye straight to her project links.
- Twenty blinking coloured text blocks, background game music, and a custom animated cursor to show off her creativity.
- No formatting at all, raw HTML and broken images, to prove she only cares about low-level code.
Show the answer
A clean, high-contrast layout that loads fast, with a few subtle hover effects that lead the eye straight to her project links.
Recruiters want a site that loads quickly, reads easily, and gets them to your project links fast. Heavy animations, background music, and slow graphics get in the way and look unprofessional; a clean, quick page signals that you know what matters.
Think first
Strategy check: naming your link
You are in Semester 2 and do not have a paid domain name yet. How should you name your free hosting link? Decide before you tap.
Show the answer
Use a free hosting subdomain and keep the name professional, matching your own name. For example, anvi-surat.github.io or firstname-lastname.vercel.app. Avoid gaming handles like coder-beast-99.net, since your link is part of your professional identity.
Watch out
The dead-link trap
A quick way to lose a recruiter's trust is a broken portfolio: missing images, 'coming soon' placeholders, or buttons that lead to an error page. If they click your project and land on an empty repo with no files or messy code with no explanation, they stop believing the rest of the page too. Before you share the link, click every link yourself and make sure it works.
Theory
Where everything comes together
Your portfolio is where all your other work lands in one place: the project descriptions you wrote with the X-Y-Z formula, the pitch you prepared for interviews, and the professor references, all sitting together on one page. It also sets you up nicely for your Semester 3 web deployment labs (BCA206-02).
Summary
Key takeaways
- A portfolio moves your profile from claims on paper to work a recruiter can actually open and try.
- Keep the layout to four clear sections: intro, skills, projects, and contact.
- Every project should have both a live link and a tidy GitHub repo behind it.
- Keep it clean and fast, and make sure no link is broken.
- Memory hook: a resume is the menu photo, a portfolio lets them taste the dish, put your work online and let it speak for you.