What I Got Wrong the First Two Times

Version one existed to check a box. I needed something online, I found a template, I shipped it in a weekend. It worked — until a recruiter asked me what I built and I realised I couldn't point to a single decision I'd made on the page they were looking at. That's a bad feeling.

Version two was more deliberate. I learned React, built it from scratch, and was genuinely proud of the code. But I'd made it for other developers. The animations were technically impressive. The layout was clean. There was almost nothing that communicated who I was or what problems I was good at solving. A designer friend looked at it for thirty seconds and said: 'It's fine. It just doesn't feel like a person made it.'

The Decision That Changed Everything

For version three, I started with one question: what do I want someone to feel sixty seconds after landing on this page? Not think. Feel. The answer shaped every layout decision — the parallax hero, the 3D element, the handwritten-style section headings. I wanted it to feel like someone who cares deeply about craft.

I also made one rule: no component goes in unless I can explain why it's there to a non-developer. That killed about forty percent of my ideas. What was left was leaner, more intentional, and for the first time, actually mine.

Key takeaways

  • Design for the feeling first — every layout decision should trace back to how you want visitors to feel, not what you want to show off technically
  • If you can't explain a UI component to a non-developer, it probably doesn't belong there
  • A portfolio that communicates your personality will outperform a technically perfect one that feels generic

Conclusion

Your portfolio is not a code showcase. It's the first conversation you have with someone who doesn't know you yet. Version three taught me that the goal isn't to impress — it's to connect. That shift changed not just my portfolio, but how I think about every product I build.

Enjoyed this article?

Vivek Kumar Singh

Vivek Kumar Singh

Technical Expert · Full Stack Cloud Engineer · Tokyo, Japan