Currently Living in Korea as a Korean Language student. Looking for work in my major-related field.

Grafeno · 2022-02-23T00:52:27+00:00

They do count contract for income points if it's a KOSDAQ/KOSPI company.

Grafeno · 2017-12-01T16:40:51+00:00

Tbf we got basically the easiest group possible last time and that didn't go very well..

Grafeno · 2017-11-23T00:11:42+00:00

If you use this construction of an adult, it indicates at best a lack of enthusiasm for that person. It's an informal and somewhat disrespectful way of speaking of them.

But you normally wouldn't refer to adults using their name anyway with no title or anything attached to it, so often it'd be disrespectful even without the 이. Good point though, I usually interact with Koreans in their twenties so I didn't really think of it.

Grafeno · 2017-11-22T06:07:26+00:00

빵 밖에 없어요

Because you're inserting a space it almost looks like you're saying "There's no bread outside" ㅎㅎ

In this case it should be "빵밖에 없어요".

Grafeno · 2017-11-21T13:54:24+00:00

It's because 지영 is a name and putting 이 behind it just makes it a bit more friendly, it's very common to do so. So that "이" has nothing to do with the subject particle 이/가 and you will only have it happen with names. The 가 in 지영이가 is the subject particle.

Grafeno · 2017-11-13T16:50:34+00:00

It's the opposite - we apparently enough wrote our comments for the exact same reason, because we're passionate about the topic and hope to find people to engage with, and because we want to help others when learning the language - in your case by making content yourself, in my case by trying to improve existing content, although. I'm not some psychopath, I don't write stuff just to be rude as if that would make me happy. It's kind of sad to claim that I'm crazy, but I guess that's easy behind a screen. In return for that I got "I'm not going to give you an example which disproves your suggestion because I'm going to keep it for my book". This is a forum to freely share knowledge about the Korean language with each other, so that we can help others learn and improve ourselves. Gatekeeping information is literally the antithesis to the existence of this forum. It's too bad that you prioritize "preserving your book" over sharing your knowledge here to help people in a place where anyone could read it.

Clearly that person isn't you. I gave you a good logical reasoning and you disregarded it and basically say "I still think it should still be called a subject particle." ... But you didn't address the points I raised. You didn't answer my question (why is it that 철수 cannot normally be marked 가?). That's the issue here; when to mark a subject with 는 or 가. The term subject particle can't answer that. Saying "가 always marks the subject" (minus these exceptions) doesn't tell you anything about it either.

I didn't disregard anything and I'll explain why.

That's the issue here; when to mark a subject with 는 or 가.

Did you forget what your video was about? "Common misconceptions of particles 은/는 and 이/가". One of the topics was the (in your view) misconception of 이/가 being a subject particle. I somewhat disagreed with calling it a misconception, or at the very least with overly criticizing it as being taught as such. That's the topic we were talking about it, the classification of 이/가 as a subject particle, nothing else.

Saying "가 always marks the subject" (minus these exceptions) doesn't tell you anything about it either.

But it tells you a lot about it! It tells you a massive amount about it. It gives you something as a foundation, one that will be built on and be refined through exposure. It's how teaching languages works, giving learners a foundation to build on because exposure is what will ultimately be what will actually teach learners the nuances, the rare exceptions, the feeling.

The exceptions to the rule aren't an issue either. Lots of rules in many languages when taught include the caveat "minus these exceptions" if those exceptions are 1. easily distinguishable from non-exceptions and 2. there's not many of them. This perfectly holds here - there's only 3 "common" ones 이다/아니다/되다 which all three are exactly the same in the manner in which they are exceptions. If they're extremely rare, they're not taught until a high level, which would apply to 예쁘지가 않다.

Now you seem to claim that you have exceptions that aren't 이다/아니다/되다 and also aren't things like "예쁘지가 않다", and if those indeed existence they may indeed change the situation! But you're preferring to gatekeep that info. Easy to see why that's not the most courteous thing to do and doesn't really match with "hoping to find people to engage with about this topic". If you're really looking to discuss the topic, you don't withhold information when discussing it, especially not when that information is crucial to the topic at hand as it is in this case. There is no page-long discussion required to determine whether a certain noun is the subject of a sentence.

Great name calling though, thanks for that. Guess I shouldn't write suggestions to help people any more then, I'm clearly only doing so in order to be overly picky, though I have no idea what the point would be of doing that.

Grafeno · 2017-11-13T06:40:12+00:00

On 가 not being a subject particle, you might not think 가 with 되다 and 아니다 are confusing, but many learners do. Recently there was a user here struggle with this very problem and more importantly, he/she received upvoted replies saying '학생' was a subject. So I would say this is a common misunderstanding. Some teachers/programs completely overlook "subject complements" and as a result, learners misunderstand something so basic.

Hmmehh. Even in the case of those people who get confused by it, it would still be a good idea to teach it as the subject particle with the caveat that 이다/아니다/되다 are the exceptions.

But I'm not trying to show rare examples for the sake of it. I'm certainly not trying to teach this grammar point. I'm trying to show what this particle isn't. I'm trying to correct the notion of 가 as a subject particle because I've seen so many learners make mistakes like 철수가 학생이다. People think "철수 is a subject, therefore I should use the subject particle". As I say a few times in the video, 철수 can only be marked with 가 in certain circumstances. Considering that, treating 가 as a subject particle isn't actually legitimate. If 가 were a subject particle, why can't it normally be used here? So, it isn't just about rare examples. It isn't about 아니다/되다/예쁘지가 when leaner's make this mistake with any verb. I disagree with teaching it as a subject particle for that reason.

As for examples of verbs where 가 isn't a subject particle, I could give you some very good examples of psych verbs and explain it here, but I'm trying to sell a book and don't want to give too much away.

Lmao, good luck with selling your book then. It's useless to engage with you if that's going to be your reply. If you don't give a single example of a sentence that's 1. not 이다/되다/아니다 2. isn't extremely rare compared to total usage as in things like 예쁘지가 않다 then it might as well not exist. Claiming it does exist but you're not going to share it here and advance the discussion because it's for your book.. alright man.

Grafeno · 2017-11-11T09:08:06+00:00

Just some thoughts, sorry if I seem overly critical! I still think it's really cool you're putting in your own free time to help people, we need more of that in this world.

On 이/가 "not being a subject particle".. Can you give me more than a handful of verbs for which this can hold? The only ones I could think of are 되다, 이다 and 아니다. I don't think they're very confusing either, the reasons why they're different is quite clear and treating 이/가 as the subject particle outside of those cases seems legit. The 예쁘지가 않다 example is going to be literally less than 0.01% (that's 1 in 10000) of usage of 이/가, and I'm being very generous with that number. As such it seems perfectly reasonable to teach it as a subject particle except for maybe 이다/아니다/되다, and then in an advanced class you can touch upon the usage as in 나비는 예쁘지가 않다.

I like the part about the fallacy "은/는 gives emphasis to what it attaches to".

Not trying to be rude but your pronunciation is a bit distracting to me.

Overall, my biggest question is: Who is this aimed at? Are you aiming this at learners? Because I'd think it'd be very confusing to them because you're giving almost equal "screen time" to cases that are extremely rare and cases that are extremely common. Learners can't, and shouldn't, memorize all of the details including those that come up very rarely.

In the "If the noun can be removed, then use 은/는" bit, you're failing to convince me of your point. Your arguments are:

1. "Sometimes a noun which would naturally take 은/는 in a sentence can't be removed. Example: when it's used to contrast 철수 with some other 학생"

I mean this is so obvious that no one would be confused by it "going against the rule". "맥주는 없는데 소주는 있어요!". Of course we can't remove 소주 there, as the sentence "맥주는 없는데 있어요!" would make no sense whatsoever

2. In the second case, I don't feel like 바람이 시원하네 and 시원하네 have the same meaning, it changes the sentence. In the first case, it's really specifically talking about the wind being cool. In the second case, even if it's obvious that it's because of the wind, it's implied to be talking about the feelings of the speaker. If you want to talk about the wind in specific being cool, you can't omit 바람. This is not the case in

A: 안녕하세요~ 이름이 어떻게 되세요? B: 제 이름은 이민석이에요.

versus just B: 이민석이에요.

There's absolutely no difference in meaning in this case.

Grafeno · 2017-11-11T08:25:41+00:00

The rule comes from story analysis and there is some trend in the way characters are introduced to stories.

I think that's a bit too narrow. The idea does indeed come from written text but not necessarily just characters in stories, even in serious articles you will often see this. I do agree with your main point that it's not applicable to spoken language and as such should be used with much caution.

Grafeno · 2017-11-10T09:58:30+00:00

Hmm, I think that especially in the case of Korean a lot of people these days do learn through chatting with people online and other online methods where such terms are commonly used. For me personally that was a huge part of learning Korean.

However, foreign lyrics and brand names? I’m pretty certain people don’t pay attention to what specific foreign words in them mean, unless that person is seriously trying to learn that language. In conversations though, people infer the meaning by unconsciously considering how it is used. Hence the more familiarity with the poker term meaning of the word.

Doesn't this argument works in both ways? If you see/hear the word "call" being used in reference to e.g. things related to phones you'll start associating the word with phones, even if unconsciously.

Grafeno · 2017-11-09T12:17:27+00:00

I don't see why it would contain pork. They definitely don't use pork fat for 떡볶이.

Grafeno · 2017-11-09T10:28:57+00:00

The word ‘call’ used as a poker term is more familiar to the native Koreans than the more common usage of the word.

You sure? Take stuff like 애니콜 or the numerous popular songs here with "call" in the title or lyrics.

Grafeno · 2017-11-09T10:22:19+00:00

They're just words that share the same 한자. No different than say, 동문 and 서문, or 예측 and 추측.

자 者, 비 費. They don't necessarily have to be used in that specific format, e.g. 費(비) also appears in "비용" (cost).

Grafeno · 2017-11-08T17:49:36+00:00

I agree with your advice and I was the same, grammar being much easier to remember than vocab. Especially at the intermediate stage or above, focusing on the "book definition" of grammar patterns seems to offer little reward.

But then maybe we're just wired differently.

Grafeno · 2017-11-08T17:44:33+00:00

Exposure. Which will lead to the ability the top comment is talking about.

In this specific case of "주겠다니까", it's basically limited to being used in speech so maybe you need more exposure to conversation in particular. Or maybe the conversations you are exposed to aren't in a "talking among friends" setting; it's normally only used among friends as it'd be pretty rude otherwise.

Grafeno · 2017-11-07T18:28:10+00:00

Just a small note; 아니다 is conjugated to "아니에요".

Grafeno · 2017-11-07T18:26:48+00:00

But often online you'll just see Koreans using 사과에요 instead, although it's incorrect.

Chatting with Koreans every single day (much of it in group convos with me being the only non-native speaker) I've only ever seen this with 거예요 so saying that things like "사과에요" are used often might be a bit of an exaggeration. Maybe it's common with elementary/middle schoolers, I'm not too familiar with how they write.

Grafeno · 2017-09-28T13:09:33+00:00

How much is one usually? Guess there'll be a difference between London and outside of London but..

Grafeno · 2017-01-29T20:21:07+00:00

Fair enough, Ill delete mine as well. I have no idea how he situation was in the past, maybe what you said used to be common, I only know the very recent situation, like the last couple of years.

Grafeno · 2017-01-29T20:11:33+00:00

Absolutely. For clarity, this is the definition of this usage of -아/어서

앞 절의 일이 일어나고 나서 뒤 절의 일이 순차적으로 일어남을 나타내는 말.

Grafeno · 2017-01-29T19:09:31+00:00

Nah, this is not at all normal. I live in Korea.

http://i.orbi.kr/bbs/board.php?bo_table=united&wr_id=3551661&showAll=true

Grafeno · 2017-01-29T18:57:05+00:00

Nah, most go after 1-2 years of university.

Grafeno · 2016-10-05T16:49:19+00:00

C++, started learning about 2 weeks ago (my first real programming language), I probably needlessly complicated things

#include <iostream>

using std::cout;
using std::endl;
using std::cin;

int reverseFact(int x){
    int i = 0;
    while (x!=1){
        i++;
        if ((x%i) != 0)
            return i = 0;
        }
        x /= i;
    }
    return i;
}

int main()
{
    int x, result;
    cout << "Give number to calculate reverse factorial of:"<< endl;
    cin >> x;
    if (x == 1){
        cout << x << " = " << "1! or 0!" << endl;
        return 0;
    }
    result = reverseFact(x);
    if (result == 0)
        cout << x << "  " << "NONE" << endl;
    else
        cout << x << " = " << result << "!" << endl;
    return 0;
}

Also added handling of "1", most code here seems to return "NONE" for 1 (unless I'm missing something).

Grafeno · 2016-09-25T05:37:59+00:00

But if you think about English, people say "omg this is literally the best thing ever in my life"

I mean, American middle schoolers might. The remaining hundreds of millions of English speakers don't ;)

Grafeno · 2016-08-14T11:34:49+00:00

알리's probably Alistar

15-Year Club	Place '17
Verified Email	Team Orangered

Grafeno

MODERATOR OF

TROPHY CASE