
Stephen Krashen: Language Acquisition and Comprehensible Input
About this video
A lecture from the 1980s by linguist Stephen Krashen on how people acquire language. He explains his comprehensible input hypothesis for second-language acquisition.
Why it appears in the archive
HN language learners cite it as the source of the comprehensible input idea and apply it to vocabulary tools and other learning.
AI-generated summary and labels from the source dataset; verify important details against the video. Source & credits.
From the Hacker News discussion
Anki is fantastic for its flexibility, but for language learning I've found I reach a point of diminishing returns after a certain point. From personal experience, I've been pretty much sold on Stephen Krashen's theory of second language acquisition[1][2], which in practice focuses on comprehensible input. lingq.com is a pretty good way to learn a second language this way. I use it by uploading an ebook in my target language. The app keeps track of the words I've learned, and highlights the words and phrases I'm still learning or haven't encountered. I can click on the word/phrase as I'm reading to see a definition or translation in the sidebar, and then mark the level at which I've learned it just like in Anki. It's pretty slow going at the start, and the texts you have to use are very basic, but pretty quickly I was reading entire YA novels with only a handful of unknown words on each page. [1] [LINK] [2] [VIDEO]
Read original comment ↗It's not a new idea being discussed in language learning circles, and 99% of the recent online discussion about this is based off of this youtube video [1] of Stephen Krashen (a linguist) talking about comprehensible input in the 80s. If I had to guess, most of the recent discussion has started again in the Japanese language learning community, as Japanese is a notoriously difficult language to acquire for anglophones. [1] [VIDEO]
Read original comment ↗I like the answers in the last part. I literally had an interview today where I quoted a professor of mine from about a decade ago. He was very upset with me about some incorrect types in my javadoc comments and told me "The only thing worse than no documentation is wrong documentation!" :) For your answer on good documentation, that's a good general answer. As you say there are lots of layers to it. Some ideas just from my current viewpoint: - From my forays into foreign language learning I picked up the linguist's Stephen Krashen's research after learning about it from my language exchange partner. One of the main themes of his research is the idea of "Comprehensible Input"(CI). CI is the idea that you acquire knowledge via exposure to new language that is at a difficulty level where you understand most of what's being said. Then you acquire these new smaller pieces of knowledge via context. I would say this is most closely related to what you mean by structure of the documentation. Obviously with some overlap with the content itself. - There's also a stronger version of CI that adds an additional piece to this, the content must be of interest to the acquirer/learner. This property is I think the closest to what I think you mean in regards to content of documentation. In my opinion reaching the first goal, Comprehensible Input, where knowledge is able to be acquired efficiently is step 1. Resources of this type can be created much more easily as there is less subjectivity a
Read original comment ↗