typo: so that the system can time features like -> so that the system can use time features like

Why do some events languish in the queue..??

Re-stickable!! haha I was searching "restickable" in dictionary.

Wow it says even if one can draw fast with drawing tools, it's better to use hand sketch style, because people will give more constructive feedback.

But actually sometimes I feel it's faster to use power point. Because I'm so bad at expressing by drawing.

=The degree of exactness with which something is copied or reproduced. src: https://en.oxforddictionaries.com/definition/fidelity

Yeah I think this's important! Even before prototyping, we have to think up ideas. We first thought up an idea about hiking and worked on it for a week. One teammate said it's not so good for this class. However at that time, other teammates got familiar with the topic, so it was not easy to change the topic at first. He gradually persuaded everybody, and we finally pivoted to better idea now :) I think this kind of "Throwing Away" mind in the early stage of design process matters.

I think it will appear in tomorrow's quiz as: c) It's important to commit strongly to design ideas in the early stages of design. :) haha

Actually the example of "AutoCad" case is highly agreed. However, I think the word "FATAL" is good. Because as one part of the article says, "Habitization(습관화: 습관적으로 에러를 끄는 것을 가리킴)" is also a problem. I often just click either yes or no without reading the error message. But when there's the word "FATAL", I stop.

Can anyone plz explain this? I don't see why Windows's cascading sub-menu is inconvenient. If sub-menu pops up, it doesn't disappear even if your mouse goes outside the menu. What's the problem?

Well is this real..?? With pie menus, we can't express long sentences, or extension pointer like in linear popup menus.

In ideal case, should 'interface model' and 'user model' the same? Because 'interface model' is what the maker PRESENT to the users, and 'user model' is what the user thinks he/she got from the maker. <한국어> [Q] 이상적이라면 인터페이스 모델과 유저 모델은 같아져야 하나요? 왜나하면 인터페이스 모델은 제작자가 유저에게 '이건 이런 시스템이다'라고 표면적으로 제공한 것이고, 유저 모델은 사용자가 '아 내가 제작자에게 받은 것은 이것이구나'라고 생각하는 것이니까요.

Wow this's interesting. The users of Twitter can learn languages from other people! By the way, is this part the spot the author mentioned as 'social computing' in the above? "Social computing is changing this situation somewhat. We'll look at Twitter in a moment, and see that you can learn some things from other people even though they're not sitting next to you." When I read this I actually thought the author was saying that the users can learn languages by 'search engine' or so. But as it turns out, it's clear a different thing. In Twitter, you constantly get the example tweets, so you can naturally learn how to use the format.

Then I think is educationally good to use MF or DM first, and then convert to CL or SD. Suppose we have to teach c programming language to starters. If there's a software which is primarily composed of MF and DM, the starter would feel it much easier to begin with. The student would just have to 'choose' commands, not having to type the full commands. In this way, the student may be able to learn even higher topics like 'system call' or 'memory management'. And when he/she gets used to it, he/she can convert to using the actual c language. <한국어> 만약 MF와 DM이 CL과 SD보다 '학습하기'가 쉽다면 그것을 이용한 소프트웨어를 개발해 보면 어떨까요? 예를 들어 초심자들에게 C언어를 가르치는 시스템이 있다고 합시다. 그런 경우 막바로 코딩을 시키는 것이 아니라 예쁜 GUI를 제시해 주고 선택지 중에서 무슨 커맨드를 실행할 것인지를 고르게 하는 것이죠. 그런식으로 C언어를 공부하다 보면 '고급' 주제들인 '시스템 콜'이나 '메모리 조작'까지 배울 수 있을지도 모릅니다. 그 후에 C언어에 익숙해진 이후라면 실제 코딩으로 갈아타는 것이죠. 물론 GUI를 사용할 때도 실제 코드는 어떻게 구성되는지 보면 좋으므로 이 article의 아래에서 얘기하는 것처럼 'self-disclosure'의 특성을 넣으면 더 좋을 것 같습니다. 그리고 C언어 뿐만이 아니라 영어 같은 것도 이런식으로 배우면 더 쉬울 수도 있지 않을까요? (영어까진 너무 멀리 갔을지도 모르겠군요 :) )

It's an organization??