A Trip to Japan Convinced Me to Build This Site

A few years ago I took a short trip to Japan. Looking back, that trip was the reason this site exists. Not because Japan itself was the inspiration — but because of how much preparation a five-day trip actually required.

What a short trip to a familiar country actually demanded

Japan is not far from Korea. The flight is about two hours. The cultures share visible surface similarities. I assumed the preparation would be light. It was not. Before the trip I spent hours researching things I had not even thought about: which IC card to buy (Suica or Pasmo, and where to top it up), how the metro transfer system handled different operators, which JR pass actually saved money on my route, how to read the timing chart at a transfer station, how to pay at a small restaurant that would not take a foreign card.

Flights and hotels were the easy part — those were sorted in an evening. The hard part was the texture of daily movement: getting from the airport to the hotel without taking a taxi, finding food without a reservation, navigating a station that had four different rail companies sharing one building. Every one of those felt obvious to a local. Every one of those required research from me.

The realization on the flight home

On the flight back I started thinking about the foreign visitors who land at Incheon every day with the same gap. They have the same hours of pre-trip research ahead of them, in a language and on a transit system that is not theirs. And the resources for them are scattered: a tourism PDF here, an old blog post there, a Reddit thread from three years ago with conflicting answers about T-money cards.

I had spent days building my Japan trip from twenty different sources. If a Korean was doing what I had just done, but in reverse, I knew exactly what I wished existed: one English-first site that did not bury the practical questions under marketing copy, that linked actual places to actual themes, and that admitted when the data was uncertain.

What Travel Code came out of

The first design problem was how to organize three thousand places without making the site feel like a phone book. The standard answer — by city, by category, by season — already existed everywhere and was not solving the matching problem. The friends I had hosted in Korea did not say "I want to visit Seoul attractions." They said "I want a calm trip, with one good market day, and one place I can take photos of, and nothing too crowded."

Travel Code came out of trying to name that shape of question. The eight codes (STAGE, TASTE, ROOT, HEAL, TRAIL, GLOW, PET, FEST) and the six pace/budget modifiers are not a marketing label. They are the categories my friends actually used when describing what kind of trip they wanted. Building the recommendation engine around them was easier than building it around traditional categories — because the categories matched how people were actually choosing.

What I want this site to be

I want this to be the site I would have wanted if I had been planning a trip to Korea instead of Japan. That means: practical answers up front, English-first writing, transparent sourcing (Korea Tourism Organization data, openly cited), and recommendations that explain why they are recommendations rather than just listing the most popular thing. The Travel Codes are how the matching works. The rest of the site is the supporting infrastructure to make that matching honest.

It is not finished. The catalog is small compared to where I want it to be, and the writing is still being improved page by page. But the direction is clear: less padding, more usefulness, English-first, and the visible reasoning behind every recommendation. That is what the trip to Japan ended up becoming.