Why I Built My Personal Website (And Why It Keeps Evolving)
A personal website started as a side project for me, but it quickly became one of the highest-leverage things I’ve built.
Unlike social platforms, my site is a place I fully control: the content, the design, and the story.
1) A single source of truth
People can find my work, background, resume, and contact links in one place.
That means less friction when:
- applying for jobs,
- sharing projects with clients,
- or connecting with other engineers.
2) Proof over claims
Anyone can say they “know React” or “build scalable systems.”
A portfolio lets me show:
- what I built,
- how I solved problems,
- and what trade-offs I made.
Screenshots, writeups, and links to live demos create trust much faster than a plain CV.
3) Career compounding through writing
Blog posts have helped me clarify my own thinking and showcase communication skills.
Even simple posts compound over time:
- one article gets shared,
- a recruiter or founder discovers my profile,
- then a project or conversation starts.
4) A safe place to experiment
My personal site is also my lab.
I use it to test:
- new UI patterns,
- performance optimization ideas,
- SEO experiments,
- and content structure improvements.
Because it’s my own platform, I can iterate quickly without waiting for product roadmaps.
5) Ownership matters
Platforms change algorithms. Accounts get limited. Reach fluctuates.
A personal website gives long-term ownership of:
- domain authority,
- technical reputation,
- and discoverable content.
That long-term control is the main reason I continue investing in it.
What’s next
I’ll keep improving this site with better case studies, richer blog content, and tighter performance/SEO.
If you’re a developer and you don’t have a personal website yet, start simple: one page, one project, one article. Then improve it every month.