It was May when I picked up React through bits and pieces I found on the internet, and boldly, without really knowing what I was doing, started developing a blog. Back then, I was gripped by a strong desire to make something with this fun new tool, and the thing that caught my eye at the time was a dev blog.

The blog I was using back then was a Jekyll-based GitHub blog, which I'd started because it looked fun, but gave up on within a few days — that was over a year ago. One of the reasons I lost interest in blogging was the stress of having to painstakingly analyze code someone else had written just to make small changes. The moment I saw a dev blog, this was roughly the train of thought running through my head.

1. Shouldn't I get back into having a dev blog too, since everyone else has one?
2. That theme I picked up and tweaked all over the place last time — the code's such a mess I don't even want to look at it again....
3. Since a static blog doesn't even need a backend role and is fairly simple, couldn't I build one with my level of React knowledge?
4. Wouldn't building my own dev blog myself feel rewarding as a developer?
5. If I built it myself, wouldn't I be able to keep maintaining it steadily? After all, I wrote all of it myself, right?

Once my thinking got that far, I started developing the blog, and working on it bit by bit after work, it ended up taking about a month or two.

I felt like the design I'd envisioned in my head turned out reasonably well, but then a problem arose. The blog was unbelievably slow. You could visibly see the process of the HTML layout appearing, then the CSS being applied and rendering afterward. And despite being static, routing somehow needed so much time too...

I kept using it as-is, but I started thinking that if I left it like this, saying "I built this myself!" would be about as embarrassing as saying "look how bad my skills are, lol". On top of that, I still needed to register it for search on Google and Naver, and if I left it like this, I'd basically be advertising this to the whole world, so I couldn't leave it as-is.

So, just two months after the first deployment, I began a full-scale overhaul. Since the reorganization process involved languages I was encountering for the first time and quite a bit of trial and error, I'm writing this development journal so that anyone suffering from similar problems can find a bit of relief.

Honestly, it's just that it's Chuseok and I'm bored.