01Who should code it
| You are | Recommendation | Why |
|---|---|---|
| Front-end developer | Code it | The site is a live sample of your skill |
| Creative developer (3D, motion) | Code it, ambitiously | Spectacle is the skill being sold |
| Back-end developer | Either; keep it minimal | Employers care more about experience and code |
| Product or UX designer | Builder or AI tool | Case studies matter more than the build |
| Photographer, illustrator, writer | Builder | Image and text presentation are what count |
02The case for coding it
A hand-built portfolio shows a front-end reviewer how you structure markup, handle accessibility, make layouts responsive and keep a page fast. It is a code sample they can open without asking. Developers on Hacker News note that for front-end roles, the site is a chance to show design sense and development skill together.
- Full control over every detail.
- A live demonstration of performance and accessibility skill.
- Free hosting on static hosts; how to host a website for free covers options.
- Something to talk through in interviews.
- A place to try new techniques without a client or employer's constraints.
03The case against it
Hacker News threads about personal sites are full of developers admitting their portfolio rebuild became a never-ending project, and several commenters warn that if the goal is a job, an elaborate site can be a distraction. Time spent picking a framework is time not spent writing case studies, which is what reviewers actually read.
04If you code it, keep it small
- 1Write the content firstIntro, three case studies, contact. Code around real words, not placeholder text that hides layout problems.
- 2Choose a light stackPlain HTML and CSS, or a static site generator; is React good for a website? covers when a framework is worth it.
- 3Make it fast and accessibleGood Core Web Vitals and clean semantics are part of the sample.
- 4Ship a first version in a weekThen improve it; a live simple site beats a perfect unpublished one, and reviewers can only judge what they can open.
- 5Host it freeGitHub Pages, Netlify or Cloudflare Pages, on your own domain.
05A middle path: start from a template, then customize
Many developers take a middle route: start from a well-made open-source template or a builder's code export, then adapt it until it is clearly theirs. You skip the blank page and the boilerplate, ship within days, and still have code you understand and can talk about. Be honest about it if asked in an interview; what you changed and why is a better conversation than pretending you wrote every line.
06If you use a builder
Pick a tool that lets you present case studies well (large images, readable text, simple navigation) and use your own domain. Spend the saved time on writing. What makes a good portfolio website? covers content, best portfolio website examples shows models, and how to make a portfolio website with AI gets a first version up quickly.
What people who tried it say
Hacker News developers split on coding portfolios: front-end developers see the site as a showcase, while many others say the build became a rabbit hole and that templates or static generators are a better use of time.
- Ask HN: Should I use React for a personal portfolio?Hacker News
Commenters advise against heavy frameworks for simple portfolios, warning the build can become a distraction from the job search.
- Ask HN: How to create a portfolio without design skills?Hacker News
Suggestions include templates, simple layouts and focusing on clear project write-ups rather than custom design.
Looking for more first-hand opinions? Search Reddit for “should i code my own portfolio”. We link the live threads rather than summarizing them, so you read them in full.
Our take
code it if the code is the point; otherwise, do not. And whichever you choose, give yourself a one-week deadline for the first version.
Where this falls short
Hiring expectations differ by company; some front-end teams care a lot about a hand-built site, others never open it. A builder-made portfolio can still impress if the case studies are strong.
If you would rather spend your time on case studies, Orlume builds the portfolio as a real Next.js project you can download on paid plans and continue coding yourself.
Free to start · No card required · Live in one click
Sources
- 1.Web Vitals · web.dev (Google)
- 2.GitHub Pages · GitHub
Researched and written by the Orlume team · Updated October 2026
Still stuck?