Portfolio

What I Built

A personal developer portfolio that serves as my personal space for showcasing my work, documenting my thinking through technical writing, and establishing my identity as a web developer. Built from scratch using modern web technologies with a focus on clarity, performance, and long-term maintainability.

Why I Built It

I needed a professional online presence that could grow with my career, but existing templates felt limiting. I wanted something that wasn't just a project gallery, but a space that reflects how I think and approach problem-solving and also extend it so I can freely express the ideas and share my creations online.

The goal was to create a foundation where people can understand me on a single medium, I also wanted to make sure that whatever I do in my professional career is documented, written and shared.

What Made Me Start

Every developer eventually faces this: How do I present myself online?

I was tired of scattered profiles across different platforms. I needed one central place where I controlled the narrative where I could show not just what I've built, but why and how I built it. I wanted to demonstrate technical skills while also proving I can communicate clearly, think structurally, and build for the long term.

Most importantly, I wanted to create something that is truly mine, not something bootstrapped, or templated from someone else's effort.

How I Did It

There isn't exactly one single line and process in making this project work, majority of the things I had to prepare are:

Picking The Right Tech Stack

I did try to consider a lot of known stacks, weighed the pros and cons, and I ultimately landed on Next JS and Sanity which was my comfort stack.

Bias aside, it's a really great pair when creating sites that gives you the feeling that you're just one click away from changing things and managing it. Coupled with a great architecture, it just makes your life much more easier.

Thinking Of A Design

Although the reason why this project has such a bland UI design is because I am not that capable in creating fancy and flashy designs, I still believe I made the right choice in making everything as simple and soothing to the user's eye.

I wanted the project to feel minimalistic, and where users can know everything about me in a single page and scroll. It also reduces the chance of people turning away from the site just seconds on getting in.

Deciding What Features To Put

This has gotta be the most gruesome part of the development, thinking. It's not easy having to pick what things you put inside a website, why it should be there, how it would help, and why it would matter in the first place.

Although, at the end of the day, I took the easy route and just built whatever came into mind little by little. Still, the initial part of the projects were a bit delayed because I was trying to manage the scope and limitations of each feature I can think and how it pairs up well with my architecture.

I am not going to dwell on the implementation part as each humans have different ways to code, construct, and build the same feature. At the end of the day, the code is just a medium of their thought process. That's just most of what I did on the early stages of the project, because even now this project is ongoing, and will still be. Forever.

What Makes It Unique

Intentional Minimalism

Unlike portfolios with flashy animations and heavy frameworks, mine prioritizes clarity over complexity. Every element serves a purpose. The design is deliberately restrained to let the content and work speak for itself.

Content Architecture That Scales

The site isn't just a static showcase, it's built to grow. Adding new projects or blog posts doesn't require restructuring; the system accommodates expansion naturally.

Technical Philosophy on Display

The site itself demonstrates my development approach:

• Performance-first: Fast load times, optimized assets, minimal JavaScript
• Maintainable code: Clean structure, well-commented, uses modern CSS features
• No over-engineering: Vanilla technologies where they suffice, no unnecessary dependencies

Blog as Thinking Documentation

Most portfolios show finished work. Mine also shows the thinking process—how I approach problems, learn new concepts, and make technical decisions. This demonstrates communication skills and depth of understanding beyond code.

Why This Matters to Me

This portfolio represents more than technical skills, it's proof of:

• Long-term thinking: Built to last years, not months
• Clear communication: Explaining complex work simply
• Professional growth: A living document of my evolution as a developer
• Intentional craft: Every decision made purposefully, not by default
• Playful creativity: Not every great idea is a professional one, build what you think is fun to build.
• Feynman Practice: You understand what you can explain easily. So structure your thoughts and deliver the words well.
• A Continuous Story: My journey, well written.

The Bigger Picture

This isn't just a portfolio, it's my professional home on the internet. A place where I control the narrative, demonstrate capabilities, and document growth. As I tackle more complex projects and refine my thinking, this site evolves with me.

It's a testament to the idea that how you present your work matters as much as the work itself.

Key Takeaway

Building this portfolio taught me that the best projects are the ones that serve multiple purposes. This site isn't just a showcase—it's a learning platform, a professional statement, and evidence of how I approach software development.

If someone wants to know what kind of developer I am, this site answers that question better than any resume could.