シャドーイング練習: The forgotten developer who saved JavaScript... - YouTubeで英語スピーキングを学ぶ
B2
It's 2009.
120 文
文が短すぎたり長すぎる場合は、Editをタップして調整してください。
1
It's 2009.
2
You're at a Hannah Montana movie,
3
and your phone won't stop buzzing with notifications from a new dating app you just downloaded.
4
Your favorite artist is supposed to be releasing a new album next year.
5
Your favorite TV show is currently being made into a movie.
6
And you're still riding high from arguing how many days are in a week on the bodybuilding.com forums.
7
Life is good, at least on the weekends.
8
Because during the week, you have to spend all day using the worst programming language ever invented.
9
A language that was famously designed in 10 days,
10
but after using it, it had you wondering what Brendan did after day two.
11
A language that every browser interpreted differently,
12
had no standard library, modules,
13
or classes, and if your primary job was to write it,
14
I'm told you were a massive loser who didn't deserve to feel love.
15
At least that's how things were in 2009.
16
But over the next decade, that sentiment changed.
17
JavaScript went from being a language that you'd never touch directly without putting on a jQuery hazmat suit first,
18
to arguably the most popular programming language in the world,
19
while JavaScript developers, despite all the stupid stickers on their MacBooks,
20
went from being considered script kitties to real programmers with actual feelings and emotions.
21
So how exactly did this mass psychosis happen?
22
There's a bunch of different reasons,
23
but in my opinion,
24
I think the most underrated was all led by a single person who has since been forgotten to time, Jeremy Ashkenis.
25
In 2009, Jeremy was a developer at Document Cloud,
26
where he had the unfortunate task of working on a heavy client-side JavaScript application,
27
which was rare at that time.
28
Having a background in Ruby,
29
but being forced to write JavaScript,
30
I assume every morning he'd wake up and think to himself,
31
wow, today might be a good day to b***ing b*** myself off the b***ing Golden Gate Bridge.
32
But unlike everyone else who had JavaScript Stockholm Syndrome,
33
Jeremy had the audacity to think he could fix it,
34
and so he did.
35
His first act was dealing with the fact that JavaScript had no standard library.
36
Again, this was 2009.
37
Although Firefox had shipped support for some array helper methods like map,
38
reduce, and foreach, Internet Explorer hadn't yet,
39
which meant you couldn't use them unless you polyfilled them.
40
So to fix this, Jeremy released Underscore.js,
41
a utility belt library that contained about 60 helper functions that made it easier to work with the Rays and Objects.
42
Now, I know that doesn't sound exciting today,
43
but building for the web was so bad back then
44
that Underscore likely did save a few people from throwing themselves off the f***ing Golden Gate Bridge.
45
Underscore got so popular that many of its features were adopted into the JavaScript language itself,
46
which eventually made it obsolete.
47
But Underscore was only Jeremy's first act.
48
Next, he decided instead of augmenting fish head JavaScript with a new library,
49
he'd have more freedom if he just created an entirely new language with large cannons.
50
Again, I can't stress this enough,
51
the JavaScript in 2009 was very different than it is today.
52
There were no classes,
53
so inheritance was done through a pattern where you'd manually attach properties to a hidden object called prototype
54
that every function had access to.
55
The only way to declare a variable had bizarre scoping rules that hoisted declarations to the top of a function,
56
whether you were aware of it or not.
57
No one really understood or cared about the difference between the equality operator and the identity operator,
58
so you'd have a bunch of type coercion happening without even realizing it.
59
And to define even a simple function,
60
you had to literally type out the word function every single time,
61
which led to some pretty ugly code.
62
By building a new language that compiled a JavaScript,
63
Jeremy could fix it without having to wait for the standards committee or browser vendors to do it themselves.
64
And even better, he could leave JavaScript the bad parts in that musty room Brendan spent 10 days in.
65
And for a while, CoffeeScript was huge.
66
Father DHH adopted it almost overnight,
67
and in 2011, it shipped as the default JavaScript preprocessor in Rails 3.1,
68
meaning the front end for every new Rails app in the world was suddenly written in CoffeeScript.
69
GitHub, Dropbox, and a long list of early 2010 startups adopted it,
70
and for a few years,
71
it was the default choice for anyone who took JavaScript seriously.
72
Today, CoffeeScript is basically dead after its best features were absorbed into JavaScript itself,
73
but every time your agent writes a class,
74
arrow function, default parameters, a spread operator,
75
does string interpolation, or destructures a value, you can thank CoffeeScript.
76
But Jeremy still wasn't done yet.
77
By 2010, he had given JavaScript a standard library with underscore,
78
and a better syntax with CoffeeScript.
79
But there was still one massive problem left.
80
There was no good way to actually structure a JavaScript application.
81
If you wanted to build a large,
82
client-side-heavy app, you would still end up with thousands of lines of spaghetti where your data,
83
DOM manipulation, and event handlers were all tangled together.
84
So in 2010, Jeremy released Backbone.js,
85
a tiny library of less than 2,000 lines of code
86
that gave JavaScript developers their first real taste of MVC on the front end.
87
It introduced models for your data,
88
collections for groups of models,
89
views for rendering, and an event system that let everything stay in sync without the need to wire it up by hand.
90
But for the first time,
91
you could build a serious client-side app without it collapsing under its own weight.
92
And with Jeremy's track record,
93
it quickly caught on, powering the early versions of Trello,
94
Airbnb, Hulu, Pinterest, and basically every other startup that needed a real front end between 2011 and 2014.
95
If you were a JavaScript developer during that window,
96
you almost certainly wrote Backbone,
97
and you probably thought it was the future.
98
But as it turns out, it wasn't.
99
Angular, Ember, and eventually React would make Backbone obsolete by taking its core ideas and pushing them further.
100
But Backbone was the library that proved you could actually build client-side heavy applications.
101
It's easy to forget how bad JavaScript used to be,
102
and even easier to forget the people who fixed it.
103
But the modern web was built on top of ideas that Jeremy Ashkenis pioneered,
104
even if no one remembers him.
105
But speaking of things you no longer have to build yourself,
106
Auth is another one, thanks to Clerc,
107
the sponsor of today's video.
108
They just launched the Clerc CLI,
109
which comes with commands that are even more powerful than the ones I saw at that human dog show.
110
Just run clerk init in any directory,
111
and it'll set up end-to-end authentication for your entire project with custom middleware,
112
auth pages, and environment variables.
113
It even detects if you're migrating from next auth or auth zero and walks you through the entire process.
114
And since they know you're using agents to do all your dirty work,
115
they also created clerk skills,
116
which ships framework-specific patterns pinned to the CLI version so your coding agent knows exactly how to use it.
117
And the clerk API command lets your agent hit the entire clerk backend API from the terminal without copy and pasting credentials.
118
Try it out for free today at the link below,
119
or just run clerk init to get started.
120
Thanks for watching, and I will see you in the next one.
アプリをダウンロード
話したすべての文をAIが採点
TRENDING
人気動画
コンテキストと背景
このビデオは、JavaScriptの歴史的な変遷と、その背後にいる重要な人物、ジェレミー・アシュケニスについて述べています。特に2009年頃、JavaScriptは多くのプログラマーから軽視されていた言語であり、開発者たちはその限界を日々感じていました。しかし、アシュケニスはその状況を変えるために行動を起こし、JavaScriptを進化させるための技術やライブラリを提供しました。彼の貢献は、JavaScriptをプログラミング言語の中で最も人気のあるものに成長させました。
日常会話のためのトップ5フレーズ
- 「今日はいい日かもしれない」 - (This might be a good day)
- 「問題を解決する」 - (To solve a problem)
- 「新しい言語を作る」 - (To create a new language)
- 「多くの人に影響を与える」 - (To influence many people)
- 「技術の進化」 - (Evolution of technology)
これらのフレーズは、テクノロジーや自己表現についての会話に役立つ表現です。特に、IELTSスピーキング対策として活用することができます。
ステップバイステップシャドーイングガイド
このビデオの内容は、英語のシャドーイングに非常に適しています。以下に、効果的に取り組むためのステップを示します。
- ビデオを観る: 初めて見る際は、全体を通して内容を理解することに集中してください。特に、YouTubeで英語学習を行う際は、視覚的な文脈が重要です。
- トランスクリプトを読む: 字幕やトランスクリプトを見ながら、話されている内容を確認します。これにより、語彙やフレーズの学習が可能です。
- シャドーイングをする: 音声を聞き取りながら、同じフレーズを発声します。この際、shadow speechやshadowspeakのテクニックを使い、発音やリズムを模倣しましょう。
- 録音して確認: 自分の声を録音し、聞き返すことで、発音や流暢さをチェックします。これにより、自分の進歩を確認できます。
- 繰り返し練習: 何度も繰り返し練習することで、徐々に自然な発音とリズムを身につけていきましょう。
定期的にこうした練習を行うことで、英語力が向上し、英語シャドーイングのスキルが高まることが期待できます。
シャドーイングとは？英語上達に効果的な理由
シャドーイング（Shadowing）は、もともとプロの通訳者養成プログラムで開発された言語学習法で、多言語習得者として知られるDr. Alexander Arguelles によって広く普及されました。方法はシンプルですが非常に効果的：ネイティブスピーカーの英語を聞きながら、1〜2秒の遅延で声に出してすぐに繰り返す——まるで「影（shadow）」のように話者を追いかけます。文法ドリルや受動的なリスニングと異なり、シャドーイングは脳と口の筋肉が同時にリアルタイムで英語を処理・再現することを強制します。研究により、発音精度、抑揚、リズム、連音、リスニング力、そして会話の流暢さが大幅に向上することが確認されています。IELTSスピーキング対策や自然な英語コミュニケーションを目指す方に特におすすめです。