Skip to main content

Initial Thoughts of Language School

Went through my first week of Korean classes. I placed into a much higher level than anticipated, which was a nice surprise. Frankly, I was terrified when I heard my placement, but when I got to the class, it turned out to not be as bad as anticipated. Here are some random thoughts from the first week.


  • My vocabulary sucks. There are many very simple words that anyone who has been in the country a year or so should probably know. I know none of them. The first embarrassing incident was minutes into the first class, when the teacher asked who was a first-time student at the school (first time: 처음). I understood the equivalent of "Who is a <blank> student at this school?" I was proud I understood that much, but didn't want to take a gamble that <blank> was "unpaid tuition" or something, so I kept my hand down. Other things that everyone knew but I was clueless about: simple everyday verbs, body parts, and the Korean name for Girls Generation.
  • My listening is also pretty bad. I think this just takes time. I can understand slow speech (sometimes), but full-speed speech is tough for me.
  • Irregular verbs are my nemesis. I never learned how to conjugate properly.
  • My teacher speaks almost completely in the most formal type of grammar. I hate it. I don't want to use the "습니다" form with anyone. It's not very practical for real life situations. I make a conscious note to answer in the "요" form, which is the standard politeness form, even if it's considered slightly rude to answer a superior's formal conjugation with a less formal one. I don't care - it's my money and I want to get good at the more useful parts of the language.
  • The first day of class, I didn't understand like half of the explanations given during the lesson, because they were meta expressions about the language. After a week, I can understand about 90% of the explanations.
  • We do a bunch of drills where we have to talk to other students. I was reading a book about language learning, and it made a fine point - if you're talking to other students, you're probably hearing a lot of incorrect usage of the language, and no one's there to correct you. Some studies have even shown people's language abilities decrease after courses that focus on talking with other students, because you simply reinforce each other's mistakes. Two things I do to mitigate this: 1) Try to correct other students' mistakes in my mind while they're speaking (if I know the mistake), and 2) Try to speak with the teacher during the dialogues.
  • We often have to read Korean from the slides. The teacher directs the reading at a pace that is approximately 25% of normal pace. This is another thing that drives me crazy - why practice speaking at a rate that's not normal? So I just try to speak as fast as I can, which means I usually finish before everyone else. I would rather they force us to speak faster than we're comfortable with.


Anyway, language learning after childhood is basically hacking your brain. I need to figure out the optimal way to accomplish it. Stay tuned.

Comments

  1. Reid1:26 PM

    1) What book were you reading about learning language? I've read a couple (like The Infinite Gift) about how kids learn languages, but haven't tried anything about how adults do so.

    2) How did you pick a language school?

    ReplyDelete
  2. Darren6:57 PM

    I was just reading bits and pieces that Google Books allowed me to read online. It was something like "The Art and Science of Learning Languages".

    I chose a language school first by finding the "top three", then going to the one that was said to focus more on listening/speaking/conversation. I might try one of the other three next session to see how it compares.

    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...
9 comments
Read more

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...
5 comments
Read more

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...
1 comment
Read more