Luyện nói tiếng Anh bằng Shadowing qua video: What is clean code? - Uncle Bob

Đang tải...
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.

Về Bài Học Này

Bạn đang luyện tập phát âm tiếng Anh với video "What is clean code? - Uncle Bob" bằng phương pháp Shadowing — kỹ thuật được Dr. Alexander Arguelles phổ biến rộng rãi.

Hãy nghe kỹ từng câu, chú ý cách người nói nhấn âm và nối âm, rồi đọc lại to và tự tin. Mỗi ngày 15–30 phút luyện đều đặn, bạn sẽ thấy phát âm chuẩn hơn.

Phương Pháp Shadowing Là Gì?

Shadowing là kỹ thuật học ngôn ngữ có cơ sở khoa học, ban đầu được phát triển cho chương trình đào tạo phiên dịch viên chuyên nghiệp và được phổ biến rộng rãi bởi nhà đa ngôn ngữ học Dr. Alexander Arguelles. Nguyên lý cốt lõi đơn giản nhưng cực kỳ hiệu quả: bạn nghe tiếng Anh của người bản xứ và lặp lại to ngay lập tức — như một "cái bóng" (shadow) đuổi theo người nói với độ trễ chỉ 1–2 giây. Khác với luyện ngữ pháp hay học từ vựng bị động, Shadowing buộc não bộ và cơ miệng phải đồng thời xử lý và tái tạo ngôn ngữ thực tế. Các nghiên cứu khoa học xác nhận phương pháp này cải thiện đáng kể phát âm, ngữ điệu, nhịp điệu, nối âm, kỹ năng nghe và độ lưu loát khi nói — đặc biệt hiệu quả cho người luyện IELTS Speaking và muốn giao tiếp tiếng Anh tự nhiên như người bản ngữ.