Why This Project

This project is already covered on the About page and in its description. However, this article goes deeper, covering its philosophy and perspective on development.

I saw some websites on similar topics where authors write down what they've learned and what projects they are working on, and I found that fascinating. I like to describe in detail what I've done — it helps me grasp things more firmly and thoroughly, and I will be able to return to my notes anytime to recall something I forgot, or to see that I spent my time on something important instead of just wasting it.

But some local tools like Google Docs, Office Word, or Obsidian are enough for this purpose. Why did I implement this idea as an online blog? Mostly because it's a perfect portfolio. I can share it with potential employers to evaluate my skills and experience, or with some friends who might be interested in areas that I explore, so they will have a trodden path.

At the time of writing this article, this project is already completed — at least its main purpose (to write and show articles) which is embedded in minimal working functionality. Even though the design leaves much to be desired and requires a little enhancement (at least for now), I'm already able to use it confidently. In the following articles, I will describe what I've already done while simultaneously recreating my code step by step from scratch, using the current version as a reference. Soon, I will add a link here to my GitHub repo where you can see the code.

During development, I used AI tools a lot, mostly Claude. Even though I used it for learning and understanding concepts, sometimes I gave in to weakness and just vibe-coded some chunks of code or whole files, leaving them alone once everything was working fine. Writing articles will help me to unravel these moments, which I can't even refactor because I don't even know what's going on there.

That's all the essential information about this project for now.