Luyện nói tiếng Anh bằng Shadowing qua video: 7 Things No Programmer Ever Wants to Hear

Đang tạo bài học...
1
Being a software engineer sucks.
2
I was told I would be working in a fast-paced, exciting environment, but in reality, I'm stuck in this cubicle, building super complex stuff that nobody understands or appreciates.
3
If I had a time machine, I would do two things.
4
One, I would tell Harambe to get away from that kid.
5
NOOOOO!
6
And two, I would go back to school to become a civil engineer, so I could work outside building stuff everyone admires, like bridges and skyscrapers.
7
Unfortunately, I haven't figured out how to build a time machine in JavaScript yet.
8
Now, I would never recommend anybody choose software engineering as a career, but if you do make bad life choices like me, you should be prepared for some really bad things to happen.
9
Like, every doctor eventually loses a patient, and every pilot eventually crashes a plane.
10
Likewise, every software engineer will eventually face a merge conflict, and that's not even very bad.
11
In today's video, we'll look at 7 different devastating text messages that no developer ever wants to hear.
12
Speaking of which, I finally started a Discord, so feel free to chat with me over there after this video.
13
We've got some t-shirts and licenses to JetBrains software to give away over there.
14
One of the biggest problems with software engineering is
15
that you don't want your friends and family to find out what you do.
16
The reason is you'll get messages like this from your uncle
17
or old roommate asking if you want to build an app together.
18
It will consist of a very dumb idea that's impossibly complex to execute, like Uber but for horses, or TikTok without the Chinese, with a $500 budget.
19
Messages like this are so painful
20
because software engineers are usually introverts who have a hard time saying no. What you'll wanna do is respond and say, hey, that's an awesome idea.
21
I would love to build it for you, but my rate is $300 an hour.
22
What they'll likely do is come back with a counter offer of $0 per hour, but 10% equity in the company, which will eventually be worth billions.
23
That's pretty much checkmate.
24
Check speaks for itself.
25
I would just recommend accepting the offer and building the app to get them to go away.
26
Now, when you're not building apps for friends and family, you should be working on your own side projects.
27
And in doing that, you'll likely use the cloud like AWS.
28
One of the worst messages you can receive is a cloud billing alert like, Hey, it's AWS.
29
Your $25 budget has been exceeded by $2.3 million.
30
Maybe you clicked the wrong button or accidentally created an infinite loop, but the important thing here is not to panic.
31
The easiest solution is to just stop using AWS and pretend nothing ever happened.
32
If Jeff ever sends his guys after you, just tell them your account got hacked.
33
That may or may not work, and
34
if it doesn't, you can at least find comfort in knowing there are many
35
other homeless people out there who simply forgot to turn off an EC2 instance.
36
Another dreaded, catastrophic thing a developer doesn't want to hear is that a production database has been dropped accidentally, along with all of your company's data that was worth billions of dollars.
37
You just made the simple mistake of dropping prod instead of dev.
38
When something like this happens, it's absolutely terrifying, but hopefully you have backups that are able to restore it back to its original state.
39
If not, now would be a good time to start looking for a new job.
40
Dropping a database is incredibly easy and can be accomplished with a single line of code.
41
You can use this knowledge to fight back against the system, as this person did here, by weaponizing SQL injection against speed cameras.
42
Dropping a database is bad, but at least it's over quickly.
43
Many developers suffer a worse fate, like this guy who got a message from his boss, assigning him to a legacy AngularJS version 1 codebase that needs to be migrated to Angular 14.
44
Sadly, the previous developer died of old age, and was the only one who had any idea how anything in this codebase worked.
45
He knew exactly how to keep his job by creating an overly complex codebase without any comments or documentation, and now it's your turn to update it.
46
Fuck my life.
47
This job will take more skill and ingenuity than building a nuclear submarine, and when you finally finish the job in a few years, no one will even notice or care,
48
because by that time it'll be time to migrate your legacy codebase into the hot new JavaScript framework of 2025.
49
Speaking of which, something a web developer never wants to hear is that a new, better JavaScript framework has been invented.
50
When you learn a JavaScript framework, you join a tribe, and that means everything outside that tribe is dangerous and terrible.
51
Now normally, you can create an echo chamber to convince yourself
52
that your chosen framework is absolutely 100% the best in every use case.
53
However, at some point, you may be convinced that a better framework does in fact exist.
54
When that day comes, you'll need to turn your back on your tribe and lose many friends in the process.
55
And it's not exactly easy to make new friends when you're a software engineer.
56
I can't sit here.
57
But one of the most annoying things that can happen to you is when a non-technical person, like a client or marketing expert, asks you to make one small change to an already finished product.
58
Like, let's just move this nav bar from the top over to the side here.
59
It should be an easy change for you to make.
60
You don't not want to look like a 10x developer, so you go ahead and do it, But it takes like 20 hours and modifications in a hundred different HTML and CSS files.
61
Then as soon as you commit your work, that same person will come back and say, you know what, I think I liked it better the first way.
62
Let's go ahead and change it back.
63
It's no secret that the most important skill of a software engineer is being able to Google things effectively.
64
That means one of the worst things
65
that can happen to you is running into a problem that nobody else has already solved for you.
66
It's painful enough when zero results come back on Google with your error message, but an even worse thing can happen.
67
You might search an error and get a single result on an obscure forum from 10 years ago, and find some dude going through the exact same problem as you.
68
As you scroll down, hoping for a well-documented and detailed solution, you find that all he posted was fixed, all good now.
69
And now you have to figure out the problem all by yourself.
70
Being the Chad that you are, you get to work, and as soon as you're about to solve the problem, you get a notification that it's time for your daily stand-up meeting.
71
Thanks for watching, and I will see you in the next one.

Từ vựng và ghi chú luyện nói cho bài học này

Video này có 71 câu và 1208 từ để luyện shadowing. Phần lời nói dài 5:14. Người nói nói nhanh, khoảng 231 từ mỗi phút, nên sẽ có nhiều chỗ nối âm và nuốt âm. 83% số từ nằm trong 3.000 từ tiếng Anh thông dụng nhất; phần còn lại nên xem trước khi luyện.

Từ vựng quan trọng trong video

15 từ đáng học trong video, kèm phiên âm và nghĩa:

TừPhiên âmNghĩa
developer danh từ/dɪˈvɛləpɚ/nhà phát triển
database danh từ/ˈdeɪtəˌbeɪs/cơ sở dữ liệu, CSDL
cloud danh từ/ˈklaʊ̯d/mây
solve động từ/sɒlv/giải quyết
painful tính từ/ˈpeɪn.fl̩/đau đớn
convince động từ/kənˈvɪns/thuyết phục
accidentally trạng từ/ˌæk.sɪˈdɛnt(ə)li/ngẫu nhiên
suffer động từ/ˈsʌfɚ/chịu đựng
uncle danh từ/ˈʌŋ.kl̩/bác, chú
suck động từ/sʌk/bú
forum danh từ/ˈfɔːɹəm/diễn đàn
incredibly trạng từ/ɪŋˈkɹɛdɪbli/khó tin nổi
fate danh từ/feɪt/số phận, số mạng
equity danh từ/ˈɛk.wɪ.ti/sự bình đẳng
loop danh từ/luːp/đường nhánh, thòng lọng

Cụm động từ bạn sẽ nghe

TừNghĩa
come back động từtrở lại, trở về
stand up động từđứng dậy
turn off động từtắt

Ngữ pháp trong video

Những cấu trúc người nói dùng nhiều nhất, kèm đúng cụm từ trong video:

Cấu trúcTrong video
Câu điều kiện if + mệnh đề, will/would + động từ — điều kiện và kết quảIf not, now would be
Câu bị động be + quá khứ phân từ — nhấn vào việc xảy ra, không phải người làmwas told · should be prepared · has been exceeded
Thì hiện tại hoàn thành have/has + quá khứ phân từ — việc đã xảy ra nhưng còn liên quan đến hiện tạihaven't figured · has been exceeded · has been dropped
Mệnh đề quan hệ who / which + mệnh đề — thêm thông tin về người hoặc vậtcompany, which will · guy who got · one who had

Phát âm cần chú ý

Người nói dùng 19 dạng rút gọn, ví dụ you'll, you're, doesn't. Hãy nói theo dạng ngắn đúng như bạn nghe.

  • Âm “sh” và “zh”: accomplish /əˈkɑm.plɪʃ/, injection /ɪnˈd͡ʒɛk.ʃən/, documentation /ˌdɑkjəmɛnˈteɪʃən/, notification /ˌnoʊtɪfɪˈkeɪʃn̩/, modification /ˌmɑdɪfɪˈkeɪʃən/
  • Từ dài — đặt trọng âm cho đúng: developer /dɪˈvɛləpɚ/, accidentally /ˌæk.sɪˈdɛnt(ə)li/, incredibly /ɪŋˈkɹɛdɪbli/, documentation /ˌdɑkjəmɛnˈteɪʃən/, notification /ˌnoʊtɪfɪˈkeɪʃn̩/

Cách luyện với video này

  1. Nghe hết video một lần, chưa cần nói, và ghi lại những từ bạn chưa biết.
  2. Bắt đầu ở tốc độ 0,75×, nói đuổi từng câu, rồi quay lại tốc độ bình thường khi đã quen.
  3. Ghi âm giọng mình rồi so với bản gốc, chú ý các từ như developer, database, cloud.

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ữ.

Phương pháp shadowing: đọc hướng dẫn từng bước đầy đủ →