シャドーイング練習: What is clean code? - Uncle Bob - 動画で英語スピーキングを学ぶ
練習モードを選ぶ
各モードは全画面の練習ルームで開きます。
80 文
文が短すぎたり長すぎる場合は、Editをタップして調整してください。
1
So I wrote to Yarna, I said, Yarna, what does clean code mean to you?
2
And he said, and this is very typical of Yarna Strewstrup, he said, I like my code to be elegant and efficient.
3
And then he said this, clean code does one thing well.
4
One thing well.
5
Now this one thing idea has been around in software for 40 years or more.
6
People are always writing about how a function should do one thing and one thing well.
7
It's a very, very old idea.
8
And Strustrip echoes it here.
9
Grady Booch, the chief scientist at Rational.
10
He wrote a book in 1988 called Object-Oriented Software Design with Applications.
11
Anybody read that book?
12
1980s, late 80s?
13
Do we have anybody who was born then?
14
Yeah, okay, good.
15
All right, so that's fine.
16
Fascinating book, very early book on object-oriented design.
17
Grady Butch is also the first person, I believe, to have the title chief scientist.
18
I think he invented that.
19
And Rational said, yeah, you can be the chief scientist, that's fine.
20
And ever since then, everybody's wanted to be a chief scientist at some company somewhere.
21
So I asked Grady, you know, Grady, what's clean code?
22
He said, clean code is simple and direct, fine.
23
And then he said this, clean code reads like well written prose.
24
Have you ever read code that read like well-written prose?
25
And let's go to Michael Feathers.
26
Michael Feathers.
27
I wrote to Michael, I said, hey Michael, what's clean code?
28
And he said, clean code always looks like it was written by someone who cares.
29
What a lovely statement.
30
That's a good attitude right there.
31
Clean code always looks like it was written by someone who cares.
32
When's the last time you read a module
33
and your thought as you were reading that module was the author cared about me.
34
The author cared about everybody else who was going to be reading that code.
35
When's the last time you had that experience, the author of this code cared about me.
36
Very interesting.
37
And by the way, it brings up a fascinating point.
38
What's your job?
39
You may think that your job is to get code to work.
40
That's not your job.
41
That's only half of your job, and it's the least important half of your job.
42
The more important part of your job is that you must write code that other people can maintain,
43
can use, can make work.
44
If you hand me code that works perfectly, perfectly, but I can't understand it, then as soon as the requirements change, that code is useless.
45
On the other hand, if you give me code that does not work, but I can understand it, I can make it work.
46
It is much more important
47
that your peers be able to understand the code you write than that the computer can understand the code that you wrote.
48
It is more important to communicate with your peers using a programming language than it is to communicate with the computer.
49
Because if you do that well, somebody will make it work.
50
The last one.
51
Ward Cunningham.
52
Who knows who Ward Cunningham is?
53
Somebody heard the name?
54
You know who that is.
55
A few of you do.
56
You'll know who he is as soon as I tell you.
57
He's the guy who invented the wiki.
58
Who's used a wiki?
59
Everybody puts their hand up.
60
Okay, good.
61
Okay, Ward Cunningham is the guy who invented the wiki.
62
He invented the wiki out of 19 lines of pearl in 1990 something or other.
63
Put it up on the website.
64
By the way, that very first wiki is still alive.
65
You can get to it if you want to.
66
The URL is c2.com.
67
The letter C and the digit 2.com.
68
That is the very first wiki ever.
69
It's still there.
70
And by the way, it's full of fascinating stuff.
71
You'll see all kinds of design pattern stuff and extreme programming stuff
72
and agile stuff because it was there at the beginning
73
and i asked ward ward what's clean code and he said this
74
you know you're working on clean code when each routine you read turns out to be pretty much what you expected
75
when's the last time you read code
76
and as you're reading it it was pretty much what you expected you're reading along
77
and you're going yeah yes yep yep yep yes mm-hmm yep yep yep when's the last time you had that experience
78
what he's saying is no wtfs per minute zero clean code
79
is no surprises no wtfs everything is pretty much what you expected.
80
That's good clean code.
アプリをダウンロード
流暢に話すために必要なすべて
AI発音採点文ごとに採点
IPA練習すべての音をマスター
単語学習自分の単語帳を作る
単語ゲーム遊びながら覚える
FOR YOU
おすすめ動画
C12
12 文
A Return to Code
Business EnglishUniversity StudentsWorking Adults
B212
159 文
My Thoughts On Cleaning
American AccentBusiness EnglishDaily ConversationUniversity Students
C12
210 文
What Software Architecture Should Look Like • Dave Farley • GOTO 2022
Business EnglishUniversity StudentsWorking Adults
C11
78 文
The easy way to keep your repos tidy.
Daily ConversationUniversity StudentsWorking Adults
C12
129 文
How to Become a Great Software Developer — Best Advice from Top-Notch Engineers
Business EnglishInterview EnglishUniversity Students
C12
176 文
3 Questions That Reveal What Your Life Is Missing - Arthur Brooks
Business EnglishUniversity StudentsWorking Adults
C13
162 文
The Secret to Business Writing: Crash Course Business - Soft Skills #3
Business EnglishUniversity StudentsWorking Adults
C12
24 文
you are programmed to doubt yourself
Business EnglishUniversity StudentsWorking Adults
C12
151 文
Wrote My Own Memory Allocator (and ran DOOM with It)
Business EnglishUniversity StudentsWorking Adults
C14
206 文
New Skills! v1.1 brings /wayfinder, /research, /implement, /to-spec, /to-tickets
British AccentBusiness EnglishUniversity StudentsWorking Adults
C13
260 文
【TED】優れたリーダーはどうやって行動を促すか/サイモン・シネック （日本語字幕）
Business EnglishDaily ConversationUniversity Students
C11
309 文
Claude Code: The Advanced Guide (99% of Devs Skip These Features)
Business EnglishUniversity StudentsWorking Adults
このレッスンの語彙とスピーキングのポイント
このC1レベルのスピーキングレッスンは、動画「What is clean code? - Uncle Bob」を教材にしています。 繰り返し出てくる語は次のとおりです：code, clean, wiki, ward, Grady。 この動画には、シャドーイング用の文が80文、単語が776語あります。 音声の長さは5:37です。 話す速さは1分あたり約138語で安定しており、シャドーイングしやすいペースです。 単語の86%は英語の頻出3,000語に含まれます。残りは練習の前に確認しておきましょう。
この動画の重要語彙
動画の中で特に難しい単語15語を、発音と意味つきで紹介します。
| 単語 | 発音 | 意味 |
|---|---|---|
| wiki 名詞 | /ˈwɪki/ | ウィキ |
| ward 名詞 | /wɔɹd/ | 被後見人 |
| scientist 名詞 | /ˈsaɪəntəst/ | 科学者 |
| invent 動詞 | /ɪnˈvɛnt/ | 発明する |
| communicate 動詞 | /kəˈmjuːnɪkeɪt/ | 伝える |
| peer 名詞 | /pɪɹ/ | 同輩 |
| module 名詞 | /ˈmɑd͡ʒul/ | モジュール |
| prose 名詞 | /ˈpɹoʊz/ | 散文 |
| routine 名詞 | /ɹuˈtin/ | 日課, ルーティン |
| requirement 名詞 | /ɹɪˈkwaɪɹmənt/ | 要求 |
| pearl 名詞 | /pɝl/ | 真珠 |
| echo 名詞 | /ˈɛk.oʊ/ | 反響, こだま |
| elegant 形容詞 | /ˈɛləɡənt/ | 優雅な, 立派な |
| digit 名詞 | /ˈdɪd͡ʒɪt/ | 数字 |
| litter 名詞 | /ˈlɪt.ɚ/ | ごみ |
動画に出てくる句動詞
| 単語 | 意味 |
|---|---|
| bring up 動詞 | 育てる |
この動画の文法
話し手がよく使っている文型を、動画の実際の表現とともに紹介します。
| 文型 | 動画での表現 |
|---|---|
| 関係詞節 who / which + 節 — 人や物について情報を加える | anybody who was · someone who cares · guy who invented |
| 受動態 be + 過去分詞 — 誰がするかより、何が起きるかに焦点を当てる | was born · was written |
| 現在完了形 have/has + 過去分詞 — 過去の出来事が今も関係している | has been · Have you ever read |
注意したい発音
話し手はyou're, you'll, can'tなど、短縮形や弱形を7回使っています。聞こえたとおりの短い形で発音しましょう。
日本語話者が苦手な音：
- /f/ — 「フ」ではなく、上の歯と下唇で出す: efficient /ɪˈfɪʃənt/, fascinate /ˈfæsɪneɪt/
- 子音の連続 — 間に母音を入れない: ward /wɔɹd/, scientist /ˈsaɪəntəst/, invent /ɪnˈvɛnt/, prose /ˈpɹoʊz/, efficient /ɪˈfɪʃənt/
この動画での練習方法
- まず声を出さずに動画を最後まで聞き、知らない単語をメモします。
- 通常の速度で一文ずつシャドーイングし、話し手のリズムに合うまで繰り返します。
- 自分の声を録音して元の音声と比べます。wiki, ward, scientistなどの単語に特に注意しましょう。
シャドーイングとは？英語上達に効果的な理由
シャドーイング（Shadowing）は、もともとプロの通訳者養成プログラムで開発された言語学習法で、多言語習得者として知られるDr. Alexander Arguelles によって広く普及されました。方法はシンプルですが非常に効果的：ネイティブスピーカーの英語を聞きながら、1〜2秒の遅延で声に出してすぐに繰り返す——まるで「影（shadow）」のように話者を追いかけます。文法ドリルや受動的なリスニングと異なり、シャドーイングは脳と口の筋肉が同時にリアルタイムで英語を処理・再現することを強制します。研究により、発音精度、抑揚、リズム、連音、リスニング力、そして会話の流暢さが大幅に向上することが確認されています。IELTSスピーキング対策や自然な英語コミュニケーションを目指す方に特におすすめです。