Pratique du Shadowing: What is clean code? - Uncle Bob - Apprendre l'anglais à l'oral avec la vidéo

Choisissez un mode d'entraînement

Chaque mode ouvre une salle d'entraînement en plein écran.

80 phrases
Si les phrases sont trop courtes ou trop longues, cliquez sur Edit pour les ajuster.
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.

Télécharger l'application

Tout pour parler couramment

Prononciation IAChaque phrase notée
Phonétique (IPA)Maîtrisez chaque son
VocabulaireEnrichissez votre lexique
Jeu de vocabulaireApprenez en jouant
FOR YOU

Vidéo recommandée

Vocabulaire et conseils d’expression pour cette leçon

Cette leçon d’expression orale de niveau C1 s’appuie sur la vidéo « What is clean code? - Uncle Bob ». Les mots qui reviennent le plus souvent : code, clean, wiki, ward, Grady. Cette vidéo contient 80 phrases et 776 mots à répéter en shadowing. La partie parlée dure 5:37. Le locuteur parle à un rythme régulier d’environ 138 mots par minute, confortable pour le shadowing. 86 % des mots font partie des 3 000 mots les plus courants en anglais ; le reste mérite d’être vu avant de commencer.

Vocabulaire clé de cette vidéo

Les 15 mots les plus avancés de la vidéo, avec leur prononciation et leur sens :

MotPrononciationSens
wiki nom/ˈwɪki/wiki
ward nom/wɔɹd/garde
scientist nom/ˈsaɪəntəst/scientifique, savant
invent verbe/ɪnˈvɛnt/inventer
communicate verbe/kəˈmjuːnɪkeɪt/communiquer
peer nom/pɪɹ/pair, pareil (pareille f)
module nom/ˈmɑd͡ʒul/module
prose nom/ˈpɹoʊz/prose
efficient adjectif/ɪˈfɪʃənt/efficace
routine nom/ɹuˈtin/routine
requirement nom/ɹɪˈkwaɪɹmənt/exigence, besoin
pearl nom/pɝl/perle
echo nom/ˈɛk.oʊ/écho
elegant adjectif/ˈɛləɡənt/élégant
digit nom/ˈdɪd͡ʒɪt/chiffre

Les verbes à particule que vous entendrez

MotSens
bring up verbeélever

La grammaire de cette vidéo

Les structures que le locuteur utilise le plus, avec les mots exacts de la vidéo :

StructureDans la vidéo
Propositions relatives who / which + proposition — une précision sur une personne ou une choseanybody who was · someone who cares · guy who invented
Voix passive be + participe passé — l’accent est mis sur ce qui arrive, pas sur qui le faitwas born · was written
Present perfect have/has + participe passé — une action passée qui compte encore maintenanthas been · Have you ever read

Prononciation à surveiller

Le locuteur utilise 7 contractions et formes réduites, comme you're, you'll, can't. Prononcez-les sous leur forme courte, telles que vous les entendez.

Les sons difficiles pour les francophones :

  • /tʃ/ et /dʒ/ — à ne pas adoucir en « ch » et « j »: module /ˈmɑd͡ʒul/, digit /ˈdɪd͡ʒɪt/, agile /ˈæd͡ʒ.aɪl/
  • /r/ anglais — langue recourbée, sans frotter la gorge: ward /wɔɹd/, peer /pɪɹ/, prose /ˈpɹoʊz/, routine /ɹuˈtin/, requirement /ɹɪˈkwaɪɹmənt/

Comment s’entraîner avec cette vidéo

  1. Écoutez la vidéo en entier une fois sans parler et notez les mots que vous ne connaissez pas.
  2. Répétez phrase par phrase à vitesse normale, en reprenant chacune jusqu’à ce que votre rythme corresponde à celui du locuteur.
  3. Enregistrez-vous et comparez avec l’original, en faisant attention à des mots comme wiki, ward, scientist.

Qu'est-ce que la technique du Shadowing ?

Le Shadowing est une technique d'apprentissage des langues fondée sur la science, développée à l'origine pour la formation des interprètes professionnels. Le principe est simple mais puissant : vous écoutez de l'anglais natif et le répétez immédiatement à voix haute — comme une ombre suivant le locuteur avec un décalage de 1 à 2 secondes. Les recherches montrent une amélioration significative de la précision de la prononciation, de l'intonation, du rythme, des liaisons, de la compréhension orale et de la fluidité.

Technique du shadowing : lire le guide complet étape par étape →