Skip to content
Anuj Purbe
All entries
3 min read
#web#nextjs#engineering

Starting this engineering portfolio

Context

Most developer portfolios follow the same template: name, about, skills, projects, contact — with percentage skill bars and a hero image. I didn't want to spend this much effort reproducing that shape.

This site is the deliverable. I want the portfolio itself to demonstrate how I reason about systems, the same way my DSA work demonstrates the fundamentals: deliberately, and with evidence.

The problem

A portfolio built from a template proves one thing — that you can apply a template. The claims it makes about skills, experience, and quality are asserted in text and never verified by the page itself. A screenshot shows what a project looked like at one moment; it says nothing about why it was built that way.

The approach

I decided the site should show its claims rather than state them:

  • DSA-first identity. The hero isn't decorative — it's PROBLEM → ALGORITHM → CODE → DATA → RESULT, the pipeline I actually think in.
  • No invented numbers. Skill bars, inflated stats, and fake "years of experience" are cut. If I haven't proven a skill in real work, it's not on the list.
  • Honest data states. GitHub and LeetCode stats load live from the APIs; when an API fails, the page says "data unavailable" instead of showing a stale screenshot of better times.
  • Project evidence. Every project page documents the problem, the approach, the architecture, and the trade-offs, so the reasoning is reviewable rather than asserted.

The stack stays unremarkable on purpose: Next.js App Router, TypeScript, Tailwind CSS, Motion, MDX. The point is that the build quality is the pitch, not the libraries.

Why projects carry their reasoning

A project page shows the result; the engineering is the reasoning behind it. Each project page in the portfolio documents the problem, the approach, the architecture, and the trade-offs — alongside the demo and the code. Screenshots answer "what did it look like"; those sections answer "how did I decide to build it this way". The screen is the output; the reasoning is the actual work.

Why the journal exists

This journal is the part of the site that can't be faked. One MDX file per entry, dated, cross-linked to the project it's actually about, with a new entry landing roughly every two weeks. It records decisions and lessons as they happen rather than as a polished after-the-fact story.

How the site is meant to evolve

  • Document the real projects properly — Hiingers and this portfolio already carry full write-ups on their project pages.
  • Add backend and system-design notes as I actually learn them.
  • Keep this journal honest: every entry is dated and cross-linked to the project it's actually about.

The site ships incrementally, and the journal is the changelog of that process. If you're reading this from the site, you're already looking at the deliverable — and the journal is the record of how it got here.

Related project

This Portfolio

Explore project

More journal entries