쉐도잉 연습: 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입니다. 화자는 분당 약 138단어의 일정한 속도로 말해서 섀도잉하기에 편한 속도입니다. 단어의 86%가 영어에서 가장 많이 쓰이는 3,000단어에 속합니다. 나머지는 연습 전에 미리 확인해 두세요.
이 영상의 핵심 어휘
영상에서 가장 어려운 단어 13개를 발음, 뜻과 함께 정리했습니다.
| 단어 | 발음 | 뜻 |
|---|---|---|
| wiki 명사 | /ˈwɪki/ | 위키 |
| scientist 명사 | /ˈsaɪəntəst/ | 과학자 |
| invent 동사 | /ɪnˈvɛnt/ | 발명하다 |
| peer 명사 | /pɪɹ/ | 동배 |
| module 명사 | /ˈmɑd͡ʒul/ | 모듈 |
| prose 명사 | /ˈpɹoʊz/ | 산문 |
| efficient 형용사 | /ɪˈfɪʃənt/ | 효율적인 |
| routine 명사 | /ɹuˈtin/ | 일과, 루틴 |
| requirement 명사 | /ɹɪˈkwaɪɹmənt/ | 요구 |
| pearl 명사 | /pɝl/ | 진주 |
| echo 명사 | /ˈɛk.oʊ/ | 메아리, 에코 |
| elegant 형용사 | /ˈɛləɡənt/ | 우아한 |
| digit 명사 | /ˈdɪd͡ʒɪ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/ — ㅍ(/p/)으로 바꾸지 말고 윗니를 아랫입술에 대기: efficient /ɪˈfɪʃənt/, fascinate /ˈfæsɪneɪt/
이 영상으로 연습하는 방법
- 먼저 말하지 않고 영상을 끝까지 듣고 모르는 단어를 적어 둡니다.
- 보통 속도로 한 문장씩 섀도잉하고, 화자의 리듬과 맞을 때까지 반복합니다.
- 자신의 목소리를 녹음해 원본과 비교하고, wiki, scientist, invent 같은 단어에 특히 주의합니다.
쉐도잉이란? 영어 실력을 빠르게 키우는 과학적 방법
쉐도잉(Shadowing)은 원래 전문 통역사 훈련을 위해 개발된 언어 학습 기법으로, 다언어 학자인 Dr. Alexander Arguelles에 의해 대중화된 방법입니다. 핵심 원리는 간단하지만 매우 강력합니다: 원어민의 영어를 들으면서 1~2초의 짧은 지연으로 즉시 소리 내어 따라 말하는 것——마치 '그림자(shadow)'처럼 화자를 따라가는 것입니다. 문법 공부나 수동적인 청취와 달리, 쉐도잉은 뇌와 입 근육이 동시에 실시간으로 영어를 처리하고 재현하도록 훈련합니다. 연구에 따르면 이 방법은 발음 정확도, 억양, 리듬, 연음, 청취력, 말하기 유창성을 크게 향상시킵니다. IELTS 스피킹 준비와 자연스러운 영어 소통을 원하는 분들에게 특히 효과적입니다.