Deciding to Build a Blog

I have always enjoyed creating things, whatever they may be. Seeing what I have made gives me energy.

Ever since entering a computer science program and beginning my studies, there has been something I have wanted to do: build my own website and service. It has been two years since I first encountered HTML, CSS, and JavaScript, and eight months since I started learning React. Over the past year, I have worked on team projects of various sizes, building services and trying different frontend and backend frameworks. I felt that the time had finally come to build a service made entirely of code I had written, .

To be honest, I do not have a brilliant idea for a service to run. That is why I started with a blog. At some point, I began to feel a real need to organize what I had studied and learned, and to keep a record of both failures and successes. Sometimes I might also write about everyday life and hobbies, rather than studying alone. So, even if it feels a little late, I decided to start blogging. Perhaps learning, documenting, and sharing more through this blog will eventually lead me to an original service of my own.

There are plenty of blogging platforms: velog, Tistory, and Naver Blog, to name a few. After looking into them, I found that platform-based blogs are heavily influenced by company policies, and each has clear strengths and weaknesses. Even if it took more time and cost a little money, I wanted to experience building a website myself, it, and it.

As I write this post, the blog has become reasonably stable. The groundwork, including SEO, the database, CI/CD, and basic design, is in place. What it needs now is good content.

I created the project on April 20, 2024, and today is June 23. About two months have passed. Working on it alongside my studies and other projects has not been easy. The commit count has passed 450, and I have run more than 100 builds for the deployed site. There is still a lot I want to create and improve. For now, though, I think it is . I plan to go back through those 450 commits from the beginning and organize the things I want to share. I used what was then the latest framework version, , but ran into many bugs, and even slightly older information online often did not apply. Even GPT-4o did not know about the App Router introduced in version 13. That left me relying heavily on and . Many of those situations differed from mine, which made the work harder. I do not want those experiences to go to waste, so I am starting this series.