Skip to main content

Address Systems are Broken in Korea and Japan

Japanese and Korean people like to contest my assertion that the address system is broken in their countries. "It's not broken, it's just different", they'll say. And of course they don't have any problems with it, since they're fluent in their respective languages.

BOOM. There it is. If you need to be fluent in the friggin' native language in order to get from one place to another, something's wrong with the addressing system.

For background, Korea and Japan both have a strange system whereby street numbers don't mean a damn thing. Okay, they mean something - they're the order that houses/buildings went up on the street. That's super useful, perhaps if you're a street historian.

As a result, most conversations over addresses go something like this:

Person 1: Hey, can you meet us at X? It's right by Yeoksam Station.
Person 2: Sure. How do I get there?
Person 1: Just go to the station, go to Exit 7, walk diagonally across the street towards the Buy the Way, turn right at the guy selling kimchi dumplings, head 200m down the alleyway, get the password from the starry-eyed cat on top of the trash can, and use it to open the hidden door next to the noraebang.
Person 2: How do I find the door if it's hidden?
Person 1: See ya soon!
Person 2: FML.

Now, you might ask, how does mail get to its destination? How do deliveries make it to offices? Well, there is a "real" addressing system that involves a postal code as well as what I guess I would call a township code. The postal code references the general area, and the township code references a small geographic block within the town. I thought this was great, cause then I could just write this down and hand it to a cabbie, who could input all of it into his GPS system.

It's not a surprise what happened. Complete FAIL.

I told the cabbie the name of the place first, and the general location. He hadn't heard of it. I told him it's a bar/restaurant, and it's by a specific station. Then I showed him the exact address from the website.

Half an hour later, we're in the middle of some residential neighborhood with streets approximately 3 feet wide and a truck full of chickens approaching us head-on. And he says, in Korean, "Here it is."

Me: Uh, no. It's a bar, not a house. It's on a main street. This clearly isn't it.
Cabbie: Then the address is wrong.

Ten minutes of phone calls later between the cabbie and the bar, we learned that the actual place was about 500m away.

In summary, I feel really bad for mailmen in Korea.

Comments

  1. In the new world we think of blocks of land as empty spaces between a grid of streets, in the Korea and in the Japan we think of streets as empty spaces between blocks of land, hence we name them. Don't confuse your insufficiencies in the Koreanese language with national incompetence.

    ReplyDelete
  2. Hey, don't strawman me. I never said anything about national incompetence. I understand the difference between the systems - I just think it's telling that even natives often need to make multiple phone calls to an establishment in order to find it.

    ReplyDelete
  3. What I found fascinating is how long those phone calls last, sometimes it takes two or three 5-10 minute phone calls between the cab driver and the person who is at and understands the destination.

    ReplyDelete
  4. Exactly! Pretty incredible.

    ReplyDelete

Post a Comment

Popular posts from this blog

Why Korean Is Hard For Native English Speakers

A couple of days ago, as an experiment, I wrote my first blog post ever in a non-English language . It was an attempt to explain some of the reasons that Korean is hard to learn for native English speakers, so I figured I might as well try to write it in Korean. Those of you who actually read Korean can see how awkward the attempt was =). In any case, the post came from an email conversation I had with The Korean from  Ask a Korean , a fantastically well-written blog about all things Korea from the perspective of a Korean who moved to the United States during high school. Since I tend to geek out on language things, I figured I might as well post part of that conversation. An edited version follows. --------- Out of the languages that I've attempted to learn so far, Korean has been the hardest. I've done a lot of meta thinking about learning Korean, and I think there are a number of reasons it's difficult for non-Koreans (and especially Westerners) to learn: 1) Obvi...

10 other things South Korea does better than anywhere else

Recently this article about 10 things that South Korea does better than anywhere else  has been making the rounds on social media, but when I first read it, I couldn't tell if it was sincere or satire. A few of the items on the list are not very positive, such as "overworking" and "using credit cards". So, I thought I would try to put together a better list. Here are 10 other things South Korea does better than anywhere else: 1) Small side dishes, a.k.a. " banchan " (반찬) Banchan are by far my favorite aspect of Korean cuisine. Rather than the "appetizer and main dish" approach of the West, a Korean meal is essentially built around small dishes. Even a 5,000 won (about $5 USD) meal at a mall food court will come with two to four banchan in addition to the "main", and often people will actually choose restaurants based  on the banchan (e.g., seolleongtang , or beef bone broth soup, places tend to have the tastiest kimchi). Ther...

Pushing Python Performance With Parallelization

TL;DR: For certain types of programs, you can take advantage of idiosyncrasies in the Python interpreter and the host operating system to create real shared memory between processes and get some pretty good parallelization. Premature optimization is the root of all evil. As a developer, you've probably heard this before, and what it means basically is that you shouldn't waste time optimizing code unless it's already doing what you want it to do. We also live in an era of seemingly unlimited resources with AWS/Google Compute, and often the easiest way to get higher throughput in your programs or service is just to pay for more instances. But sometimes it's fun to see what sort of performance we can get on a simple laptop (and save some cash at the same time). So anyway ... I've been working on this thing, and it took too damn long to run, and I needed to run it lots and lots of times ... so, it was time to optimize. Basic optimization has two main steps: 1) P...