Why I Added a Blog to My Portfolio

You might have noticed something new here—there’s a blog now.

Here’s the reason: in my old setup, I was mixing too much together. Personal journaling, technical notes, even portfolio updates—all crammed into one space. It felt messy.

So I decided to split things up:

• Portfolio stays professional. A clean showcase of projects, code, and technical writing.

• Journaling goes personal. I’m moving that part to a separate space, where I can write freely without worrying about whether it “fits” my portfolio.

This also means a domain shuffle:

• grish.me → will hold the personal journal.
• nory.tech → will become my main portfolio and blog for tech + creative work.

This blog is the first step in that shift. Think of it as a reset button. A clearer boundary between my personal life, professional life, and technical explorations.

From now on, my journaling blog will be where I drop everything—thoughts, feelings, movie reviews, music I like, random vibes. That’s the personal side.

This portfolio blog, though, is different. It’s not as polished as my dedicated journaling site, and honestly, it’s still a work in progress.

Here’s what happened: I redesigned my portfolio, added the blog feature, and worked on it here and there over a month. But then, two weeks ago, disaster. I had an issue with my Arch Linux install (kernel problem), had to reinstall, and lost my progress.

Why? Because I never pushed the changes to GitHub. Bad habit. I had the code locally, but I didn’t push it to the remote. So when the reinstall wiped everything, all that progress was gone.

That’s why things might feel clunky right now. It’s not fully refined, and that’s fine. I’ll fix it later. For now, I just wanted to get this blog started instead of waiting until everything’s perfect. I decided to build this version of the blog as fast as possible. Not as refined, not as polished as before—just make it work. That’s the vibe right now.

The same thing happened with my journaling site too. I had a full redesign in mind, even coded most of it, but then I lost the progress. Haven’t touched it since. It’s still waiting for me to rebuild.

I know I haven’t published much blogging here yet, but I have a lot planned. Most of my notes live in Obsidian right now—rough drafts, ideas, half-finished posts. It’s just a matter of rewriting and moving them here.

Some people even asked me about Devlog 2. Funny story: it was already on the site, but I forgot to set the published flag to true, so nobody could see it. That’s on me. I’ll fix it and republish soon.

I’ve also written up to Devlog 6, but those need refining before I drop them here. Same with my technical notes—I’ve got plenty stored away, just waiting to be shaped into proper posts.

So yeah, even if it looks quiet now, there’s a lot more coming.

It’s just the beginning, but it feels like the right direction.

A lot of people asked me about comments on my blog. I didn’t want to add some heavy authentication system just so people could leave a thought—that feels like friction.

So I tried a different approach: I built a simple form that sends the comment straight to my email. No accounts, no sign-ins, no hassle.

Now if you want to leave a comment, you don’t even have to email me manually—the form does it for you. Simple and direct. I also want to thank everyone who emailed me asking, “When’s the next journal coming out?” Honestly, I loved getting those messages.

The truth is—I haven’t done much journaling lately. I had so many plans, but they didn’t work out. That’s on me. Starting now, I’m committing to posting a weekly journal.

Thank you again for the kind words and encouragement.

One last note: I haven’t touched SEO for this site yet. So it might be hard to stumble across it. If you’re reading this right now, consider yourself lucky—you found it anyway.