I honestly thought this portfolio would take me a few days.
Create a homepage. Add some projects. Write an About page. Deploy it.
Simple... right?
Not even close.
Somewhere along the way, this portfolio stopped being just another personal website.
It became my playground.
Every single day I discovered something new.
A better animation.
A cleaner layout.
A different way to structure components.
A more elegant user experience.
Every time I learned something, I couldn't resist opening the code again and asking myself,
«"What if I improve this too?"»
That one question probably doubled the amount of work.
And I'm completely okay with that.
There were nights where I wasn't adding features.
I was chasing bugs.
A missing image that somehow worked yesterday.
An OAuth callback refusing to authenticate.
A blog page crashing because React didn't like a Date object.
Markdown rendering issues.
Broken image paths.
Git conflicts.
Deployment failures.
404s.
Authentication loops.
One bug would disappear...
...and another would quietly appear from somewhere else.
Sometimes I spent hours fixing something that eventually turned out to be a single misplaced line of code.
Those are the moments that test your patience.
The funny part?
Every bug taught me something.
I learned more while debugging than while writing new features.
I started understanding how Next.js actually works.
How GitHub OAuth flows happen.
How Decap CMS communicates with GitHub.
How Markdown gets parsed.
How build systems behave.
How browsers exchange messages between popup windows.
How tiny implementation details can completely change the behavior of an application.
None of those lessons came from reading documentation alone.
They came from breaking things.
Fixing them.
Breaking them again.
And eventually understanding why they broke in the first place.
This portfolio slowly became much bigger than I had imagined.
It now has a custom-built blog.
GitHub-powered CMS.
Responsive layouts.
Animated interactions.
Dynamic SEO.
Comment system.
Content management.
Sharing.
And many tiny details that most visitors will probably never notice.
But I notice them.
Because I remember the bug that made each one necessary.
One thing I realized during this journey is that software is never really finished.
Every time I open the project, I find something I want to improve.
Sometimes it's performance.
Sometimes it's accessibility.
Sometimes it's typography.
Sometimes it's just moving a button by a few pixels because it "feels" better.
That curiosity keeps the project alive.
There were definitely moments when I wondered,
"Why am I spending three hours fixing something that nobody will even notice?"
Then I realized...
I'm not just building a portfolio.
I'm building myself.
Every feature teaches me something.
Every bug makes me a better developer.
Every deployment gives me confidence.
Every mistake becomes experience.
One day this portfolio will probably look completely different.
New technologies.
New ideas.
New designs.
New features.
But I hope one thing never changes.
That excitement of opening the project late at night and thinking,
«"I have one more idea..."»
Because that's where the best improvements have always started.
And honestly...
I don't think this portfolio will ever be finished.
Maybe that's the best part.
Thanks for reading.
If you've ever stayed awake longer than you planned because one stubborn bug refused to lose, you're definitely not alone.
Sometimes the best code isn't written during working hours.
It's written after midnight—with a cup of tea, too many browser tabs open, and the determination to make one more thing work.