Shadowing Practice: What is clean code? - Uncle Bob - Learn English Speaking with Video

Choose a practice mode

Each mode opens a full-screen practice room.

80 sentences
If sentences are too short or too long, click Edit to adjust them.
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.

Download App

Everything you need to speak fluently

AI PronunciationScore every sentence
IPA PracticeMaster every sound
VocabularyBuild your word bank
Vocab GameLearn while playing
FOR YOU

Recommend Video

Vocabulary and speaking notes for this lesson

This C1 speaking lesson is built on the video “What is clean code? - Uncle Bob”. The speaker keeps coming back to these words: code, clean, wiki, ward, Grady. This video has 80 sentences and 776 words to shadow. The speech runs for 5:37. The speaker talks at a steady 138 words per minute, a comfortable pace for shadowing. 86% of the words are among the 3,000 most common in English; the rest is worth studying before you start.

Key vocabulary in this video

The 15 most advanced words in the video, with pronunciation and meaning:

WordPronunciationMeaning
wiki noun/ˈwɪki/A collaborative website which can be directly edited merely by using a web browser, often by anyone who has access to it.
ward noun/wɔɹd/The action of a watchman; monitoring, surveillance (usually in phrases keep ward etc.)
scientist noun/ˈsaɪəntəst/One whose activities make use of the scientific method to answer questions regarding the measurable universe. A scientist may be involved in original research…
invent verb/ɪnˈvɛnt/To design a new process or mechanism.
communicate verb/kəˈmjuːnɪkeɪt/To impart or transmit (information or knowledge) to someone; to make known, to tell.
peer noun/pɪɹ/Somebody who is, or something that is, at a level or of a value equal (to that of something else).
module noun/ˈmɑd͡ʒul/A self-contained component of a system, often interchangeable, which has a well-defined interface to the other components.
prose noun/ˈpɹoʊz/Language, particularly written language, not intended as poetry.
efficient adjective/ɪˈfɪʃənt/Making good, thorough, or careful use of resources; not consuming extra. Especially, making good use of time or energy.
routine noun/ɹuˈtin/A course of action to be followed regularly; a standard procedure.
requirement noun/ɹɪˈkwaɪɹmənt/A necessity or prerequisite; something required or obligatory. Its adpositions are generally of in relation to who or what has given it, on in relation to whom…
pearl noun/pɝl/A shelly concretion, usually rounded, and having a brilliant luster, with varying tints, found in the mantle, or between the mantle and shell, of certain…
echo noun/ˈɛk.oʊ/A reflected sound that is heard again by its initial observer.
elegant adjective/ˈɛləɡənt/Characterised by or exhibiting elegance; having grace, refinement, or tasteful simplicity.
digit noun/ˈdɪd͡ʒɪt/A position in a sequence of numerals representing a place value in a positional number system.

Phrasal verbs you will hear

WordMeaning
bring up verbTo mention.
hand up verbTo deliver an indictment (e.g. to a judge).
read along verbTo read together with another person, or with another presentation (TV etc)

Grammar in this video

The structures the speaker uses most, with the exact words from the video:

StructureIn the video
Relative clauses who / which + clause — extra information about a person or thinganybody who was · someone who cares · guy who invented
Passive voice be + past participle — the focus is on what happens, not who does itwas born · was written
Present perfect have/has + past participle — a past action that still matters nowhas been · Have you ever read

Pronunciation to watch

The speaker uses 7 contractions and reduced forms, such as you're, you'll, can't. Say them the short way, as you hear them.

How to practise with this video

  1. Listen to the whole video once without speaking and note the words you do not know.
  2. Shadow it sentence by sentence at normal speed, repeating each one until your rhythm matches the speaker.
  3. Record yourself and compare with the original, paying attention to words like wiki, ward, scientist.

What is the Shadowing Technique?

Shadowing is a science-backed language learning technique originally developed for professional interpreter training and popularized by polyglot Dr. Alexander Arguelles. The method is simple but powerful: you listen to native English audio and immediately repeat it out loud — like a shadow following the speaker with just a 1–2 second delay. Unlike passive listening or grammar drills, shadowing forces your brain and mouth muscles to simultaneously process and reproduce real speech patterns. Research shows it significantly improves pronunciation accuracy, intonation, rhythm, connected speech, listening comprehension, and speaking fluency — making it one of the most effective methods for IELTS Speaking preparation and real-world English communication.

Shadowing technique: read the full step-by-step guide →