Skip to main content

Honorific Rudeness

The Korean language is filled with honorifics, meaning there are different ways of addressing people according to rank and seniority. Additionally, like the other main Asian languages, there's a word for "foreigner" that you hear over and over again. In Korean, it's 외국인 ("oegugin", sounds like "way-goo-geen" with hard g's). It's impossible to go anywhere in Korea and not hear this word. Just like the word "foreigner" in English, it can be used in different ways. It's often a non-malicious way of talking about Westerners, since it's slightly shorter than 외국사람. But it can also have the negative connotation of calling someone a foreigner, an outsider.

On an unrelated note, Koreans often address each other by title, like "Teacher", and they add 님 ("nim") to the end as an honorific (e.g., 선생님, or Teacher).

Which brings me back to my story. I went to a coffee shop the other day, and as I'm paying, I could have sworn I heard one of the girls behind the counter say to the other one "외국인님 있어요", which is a strange combination of "foreigner" and the honorific. Like I said, I don't speak Korean, but it would probably be equivalent to calling someone "Mr. Foreigner" in America. I laughed, and then she looked away embarrassed, because foreigners aren't supposed to understand Korean. Heh.

Comments

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...