Most developers treat a portfolio as a static page — a list of skills, a few projects, and a contact form.
I decided to do it differently.
This portfolio is not just to show what I’ve built, but to document how I think, learn, and make decisions as a developer.
Context
Over the last couple of years, I’ve worked with multiple tech stacks — Node.js, Angular, React, WordPress — across different kinds of projects.
What I realized was this:
Skills alone don’t reflect problem-solving ability.
So instead of only showcasing finished work, I want this space to show the process behind the work.
What I’m Doing Differently
- Writing posts alongside building projects
- Explaining why I chose a certain approach, not just what I used
- Documenting mistakes, refactors, and improvements
- Treating this portfolio as a long-term knowledge base
The goal is clarity — for others, and for my future self.
Key Learnings So Far
- Clean thinking matters more than complex code
- Consistency builds credibility faster than perfection
- Real-world decisions are rarely black and white
- Writing improves technical clarity