Luyện nói tiếng Anh bằng Shadowing qua video: Interview with Big Data engineer in 2026.
Chọn chế độ luyện tập
Mỗi chế độ mở một phòng luyện tập toàn màn hình.
168 câu
Nếu các câu quá ngắn hoặc quá dài, hãy bấm Edit để chỉnh sửa.
1
We built a real -time pipeline
2
So leadership can ignore insights at millisecond speeds
3
What was the question?
4
Okay, sorry.
5
I had quick
6
Problem in database, but no worries all 200 tetabytes are recovered
7
Big data most companies don't actually have big data
8
They have medium data.
9
Big data is anything that crushes Excel.
10
We actually have two big data for fault tolerance.
11
Two wrongs don't make a right, except in a distributed database.
12
Big data is different math.
13
1 plus 1, 1 .9.
14
95 % confidence interval.
15
Our 15 million raw data set has 800 columns.
16
The rows aren't wide, they are panoramic.
17
If the joint fits in memory, it belongs in Postgres.
18
Our architecture preserves every invariant except the budget.
19
Our cloud bill was $340 ,000.
20
We don't know if the processing even ran.
21
That was just observability.
22
We support real -time processing, of course.
23
Unless the event arrives early, late, duplicated, malformed, reordered, eventual consistency was too hard.
24
So we went with immediately inaccurate.
25
70 % of records are accurate.
26
It's higher than the weather forecast.
27
The numbers are not wrong.
28
They are early.
29
Wait, two, three, maybe four days, they will be late.
30
It's almost interactive analytics.
31
Final numbers mean numbers we have stopped refreshing.
32
The slide says we handle billions of events.
33
It does not say we handle them well.
34
It is only truly idempotent if all availability zones go down equally during the outage.
35
Management.
36
Management asked us to build a data lake, but it wasn't scalable enough.
37
So McKinsey asked us to build a data swamp.
38
The project was declared successful before all the metrics arrived.
39
We call that watermarking.
40
Dashboard is green because the job that checks if the dashboard is wrong is red.
41
Ah, what happened here?
42
Let me quickly roll back 30 billion events.
43
A production workaround becomes durable the moment the engineer who wrote it leaves.
44
Yes.
45
We removed an unused column and it broke Portugal.
46
The bug has existed for eight years.
47
At this point it's an interface.
48
Quick Slack message.
49
20 terabytes lost again.
50
This is our architecture.
51
Very simple.
52
Kafka, Airflow, Databricks, Flink, Spark, SQL, Iceberg, S3, Presto, DBT.
53
What does DBT stands for dialect behavioral therapy.
54
We need that to avoid going crazy.
55
We have the most modern stack in the industry.
56
Only 10 % is COBOL.
57
HDFS is not dead.
58
It's waiting for someone with root access.
59
We migrated from Kroon to Airflow for reliability.
60
Then we wrote a Kroon job to check if Airflow silently died.
61
We would switch from Databricks to Excel if it wasn't for date parsing.
62
We are a data driven company of course.
63
Every week somebody reads the invoices out of PDFs and types the data into Excel.
64
Running on Kubernetes.
65
We moved from Hive tables to Iceberg tables because we wanted the metadata to fail with better governance.
66
Last week, we had some ransomware attack.
67
We lost the backups, yes.
68
Whenever we lose a backup, we reconstruct what the customer did from the logs.
69
No, that's one of our industry's best practices.
70
Our customers didn't even know.
71
To be honest, most of our customers don't even use our product anyway.
72
The board deck says petabyte scale, yeah.
73
Scale is a direction, not a quantity.
74
I checked with a legal.
75
Management says one petabyte.
76
I checked, yeah.
77
We only process 18 terabytes, but we round up.
78
Our P99 is four minutes.
79
But the P50 is excellent.
80
And most people are median.
81
Streaming gets simple once you understand watermarks.
82
Event time, processing time, state, back pressure.
83
Batch and streaming produce different numbers.
84
We average them.
85
Our recommendation pipeline had three hours of Kafka lag.
86
So technically it was a real time communication for your past self.
87
Kafka rebalanced so often I started listing it under team building activities.
88
We decoupled storage and compute.
89
Now the storage team and the compute team have separate outages.
90
Ah, again, we lost the logs from Tuesday.
91
The data team, the data team has excellent isolation.
92
We haven't spoken to product in seven months.
93
All problems become your problems at one terabyte an hour.
94
Exactly once processing is easy.
95
You just need two topics, transactions, offsets, recovery state and a relaxed interpretation of easy.
96
GDPR in a data warehouse.
97
This is a funny joke.
98
We anonymize the data by removing the column name.
99
We persist it in places nobody knows how to query.
100
The only thing in this company with strong durability is a bad architectural decision.
101
Salary, job, security, holidays, pick two, a CIP compliant.
102
Can we have this by Friday?
103
In distributed systems, what does Friday mean?
104
Before the meeting is only a partial order.
105
The project isn't late.
106
The clocks just disagree.
107
It's a distributed organization.
108
Every quarter we solve capacity problems by increasing input.
109
We maintain system availability by shedding JIRA tickets.
110
Last year, they fired 80 % of our team as part of our operational transformation.
111
They should have used CRDTs instead.
112
A backfill is when you fix one historical bug by introducing a brand new historical bug.
113
The Snowflake warehouse runs a two -second query every minute.
114
A very sophisticated way of never letting it turn off.
115
Artificial intelligence?
116
No. We still rely on humans, a single point of failure.
117
Yes, David.
118
The game.
119
You pull something from the bottom, everything falls apart.
120
It's educational game for industry.
121
Back 2016, learning Hadoop in the simple 760 steps.
122
That's right.
123
Hadoop certified.
124
Cloudera certified.
125
Cloudera no longer offers this cert.
126
We migrated to Abachi iceberg this year.
127
Quick 43 months migration.
128
We still use protobuf.
129
Yes, we are still confused, but at least confused strongly type.
130
Some say data is the new oil.
131
We cannot stop producing it and we will pay to clean it up for years.
132
From what I see, data is the new asbestos.
133
The AI team spent four million and it called investment.
134
I spent three hundred forty thousand.
135
It is called a review.
136
I'm in FinOps review every Thursday.
137
The AI team has never ever been to FinOps.
138
They have a different word for money.
139
My cluster is a cost center.
140
Their cluster is a strategy.
141
Same rack in AWS where I make, there are my glasses.
142
Duh!
143
Ah, only disk usage 80%.
144
This is sweet spot.
145
A soft outage is when the checkpoint directory grows faster than S3 versioning can build.
146
Back in the days, big data means you bring the intelligence to the data.
147
That's why I go straight to big data center.
148
We have two big data centers for fault tolerance.
149
I wanted to become simple app developer.
150
Take app, build it, host it on railway, no problems.
151
No thinking required.
152
I can go on holidays.
153
But the team came with Airflow Graph.
154
We use what?
155
1, 2, 3, 4, 13, 14, 23, 60, 400 services just to clean the locks.
156
Whole dashboard?
157
You need whole company.
158
I am on call today, yes.
159
As you can see.
160
Oh, I turn my phone off.
161
If it burns, it burns.
162
I don't have keys to service anyway.
163
What am I gonna do?
164
I'm not ignoring Slack.
165
I'm just following our load shedding policy.
166
Don't ship late and don't ship too early.
167
Ship peacefully.
168
Thank you, Railway, for sponsoring this video.
Tải Ứng Dụng
Mọi thứ bạn cần để nói trôi chảy
Chấm điểm AIChấm từng câu nói
Luyện IPAThành thạo mọi âm
Từ vựngMở rộng vốn từ
Game Từ vựngHọc qua chơi
Cùng kênh
FOR YOU
Video gợi ý
C11
358 câu
It’s not just you
Daily ConversationUniversity StudentsWorking Adults
C11
77 câu
The Secret Sauce Behind NoSQL: LSM Tree
Daily ConversationUniversity StudentsWorking Adults
C13
134 câu
How Uber Scaled from One Server to 150 Million Reads Per Second
Daily ConversationUniversity Students
C12
118 câu
The Anatomy of Fraud
Daily ConversationUniversity StudentsWorking Adults
C11
398 câu
Sec Growth DataScience staff meeting Sep 14 2022
Daily ConversationUniversity StudentsWorking Adults
C138 câu
"Dive Deep" Leadership Principle Explained by Amazon CEO Andy Jassy
Daily ConversationUniversity StudentsWorking Adults
C11
689 câu
Database Sharding! Designing Data-Intensive Applications chapter 6
Daily ConversationUniversity StudentsWorking Adults
C11
389 câu
They JUST Accidentally Revealed the Truth: The AI Bubble
Daily ConversationUniversity StudentsWorking Adults
B21
220 câu
How Modern Data Teams Work (Engineer, Analyst, Scientist, Architect, ML)
Daily ConversationUniversity Students
C1231 câu
Redis Crash Course - the What, Why and How to use Redis as your primary database
Daily ConversationUniversity StudentsWorking Adults
C11
532 câu
How an Ex-Googler Accidentally Founded a Database Company
Daily ConversationUniversity StudentsWorking Adults
C11
37 câu
How Anthropic uses Claude in Product Management
Daily ConversationUniversity StudentsWorking Adults
Từ vựng và ghi chú luyện nói cho bài học này
Bài luyện nói này dựa trên video “Interview with Big Data engineer in 2026”. Video này có 168 câu và 1183 từ để luyện shadowing. Phần lời nói dài 8:34. Người nói giữ tốc độ đều, khoảng 138 từ mỗi phút, vừa sức để nói đuổi theo. Chỉ 76% số từ nằm trong 3.000 từ tiếng Anh thông dụng nhất, nên từ vựng khá khó.
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 âm | Nghĩa |
|---|---|---|
| ignore động từ | /ɪɡˈnɔː/ | lơ, lờ |
| railway danh từ | /ˈɹeɪlˌweɪ/ | đường sắt, đường ray |
| architecture danh từ | /ˈɑː.kɪˌtɛk.t͡ʃə/ | kiến trúc |
| log danh từ | /lɔɡ/ | gỗ tròn |
| column danh từ | /ˈkɒləm/ | cột |
| database danh từ | /ˈdeɪtəˌbeɪs/ | cơ sở dữ liệu, CSDL |
| warehouse danh từ | /ˈwɛə(ɹ)haʊs/ | kho hàng, kho |
| topic danh từ | /ˈtɑpɪk/ | chủ đề |
| cloud danh từ | /ˈklaʊ̯d/ | mây |
| solve động từ | /sɒlv/ | giải quyết |
| arrive động từ | /əˈɹaɪv/ | đến |
| introduce động từ | /ˌɪntɹəˈdus/ | giới thiệu |
| salary danh từ | /ˈsæləɹi/ | lương |
| slide danh từ | /ˈslaɪ̯d/ | cầu trượt, cầu tuột |
| recover động từ | /ɹɪˈkʌvɚ/ | lấy lại, giành lại |
Cụm động từ bạn sẽ nghe
| Từ | Nghĩa |
|---|---|
| turn off động từ | tắt |
Những câu đáng luyện lại
Các câu ngắn, trọn ý trong video mà bạn có thể dùng lại khi giao tiếp hằng ngày:
- We don't know if the processing even ran.
- No, that's one of our industry's best practices.
- Our customers didn't even know.
- We haven't spoken to product in seven months.
- What am I gonna do?
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úc | Trong video |
|---|---|
| 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ại | have stopped · has existed · haven't spoken |
| 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àm | are recovered · was declared · is called |
Phát âm cần chú ý
Người nói dùng 17 dạng rút gọn, ví dụ don't, I'm, wasn't. Hãy nói theo dạng ngắn đúng như bạn nghe.
- Âm “sh” và “zh”: artificial /ˌɑː.tɪˈfɪʃ.əl/, interpretation /ɪnˌtɜːpɹəˈteɪʃən/, operational /ˌɑ.pəˈɹeɪ.ʃə.nəl/, transaction /tɹænˈzækʃən/, transformation /ˌtɹæns.fɔɹˈmeɪ.ʃən/
- Từ dài — đặt trọng âm cho đúng: architecture /ˈɑː.kɪˌtɛk.t͡ʃə/, availability /əˌveɪ.ləˈbɪl.ɪ.ti/, artificial /ˌɑː.tɪˈfɪʃ.əl/, interpretation /ɪnˌtɜːpɹəˈteɪʃən/, operational /ˌɑ.pəˈɹeɪ.ʃə.nəl/
Những âm người Việt thường gặp khó:
- Cụm phụ âm cuối — đọc đủ từng âm, đừng nuốt âm cuối: confused /kənˈfjuːzd/, tolerance /ˈtɑ.lə.ɹəns/, solve /sɒlv/, relax /ɹɪˈlæks/, mathematics /mæθ(.ə)ˈmæt.ɪks/
- Âm /tʃ/, /dʒ/ và /ʒ/ — tiếng Việt không có, đừng đọc thành “ch” hay “gi”: architecture /ˈɑː.kɪˌtɛk.t͡ʃə/, usage /ˈjuːsɪd͡ʒ/, architectural /ˌɑɹkɪˈtɛkt͡ʃəɹəl/, batch /bæt͡ʃ/, eventual /ɪˈvɛn.t͡ʃu.əl/
- Âm /æ/ — mở miệng rộng hơn âm “e”: backup /ˈbækˌʌp/, salary /ˈsæləɹi/, relax /ɹɪˈlæks/, transaction /tɹænˈzækʃən/, transformation /ˌtɹæns.fɔɹˈmeɪ.ʃən/
Cách luyện với video này
- 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.
- Nói đuổi từng câu ở tốc độ bình thường, lặp lại mỗi câu đến khi nhịp của bạn khớp với người nói.
- Ghi âm giọng mình rồi so với bản gốc, chú ý các từ như ignore, railway, architecture.
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ữ.