쉐도잉 연습: English for Developers: Project Kickoff Meeting | Listening Practice - 영상으로 영어 말하기 배우기

연습 모드 선택

각 모드는 전체 화면 연습실로 열립니다.

249 문장
문장이 너무 짧거나 길면 Edit를 눌러 조정하세요.
1
From clean code to clear communication, welcome to English Not Null, where you learn to present your work with confidence and precision.
2
Have you ever sat in a project kickoff where the launch
3
date was already on the first slide before anyone asked the developers?
4
This team runs the website that sells movie tickets for 40 theaters.
5
Today, they start building the mobile app.
6
And somebody in that room has to be the one to say, that date worries me.
7
Thanks for coming everyone.
8
This is the kickoff for the mobile app.
9
By the end of this hour, I want us to agree on four things.
10
What we're building, when, who owns what, and what could go wrong.
11
Start with the why.
12
Why an app and why now?
13
Because seven out of ten tickets we sell are bought on a phone, on a website that was built for a laptop.
14
People pinch and zoom to pick a seat and a lot of them give up before they pay.
15
I pulled that number last month actually.
16
On a laptop, six people in 10 who pick a seat end up paying.
17
On a phone, it's four.
18
So the company wants an app, and it wants it for the Spring Film Festival.
19
We sponsor the festival, and opening night is March 19th.
20
That's the date on the slide.
21
March 19th.
22
So 16 weeks from today.
23
And the date's already on a slide.
24
It's on a few slides, honestly.
25
Marketing has booked the campaign.
26
Mike, I can see your face and we'll get to the date, I promise.
27
But we can't judge a date until we know what's in it.
28
So scope first.
29
Scope first.
30
Oh, and one small thing before that, the project channel is called New Mobile App Final 2.
31
Somebody please find a better name before we leave this room.
32
Here's my list for the first release.
33
Six things.
34
You see what's playing and when, you pick your seats and you pay.
35
Your tickets live in the app.
36
You earn and spend your member points.
37
And you order snacks ahead so they're ready when you walk in.
38
Can I start at the bottom?
39
Snack orders aren't a feature.
40
They're a second product.
41
Every theater has its own menu and its own prices, and somebody in the kitchen needs a screen that says an order came in.
42
None of that exists today.
43
Well, I had to try.
44
Snack orders are out of the first release.
45
I'd take one more out, Member points.
46
No. Sorry, but no. Points are the reason somebody installs an app when the website already works.
47
And marketing's whole message is, members get double points in the app.
48
I'm not against points.
49
I'm asking what we can finish and test in 16 weeks.
50
Can I split it?
51
Points are really two things.
52
Earning them is easy to test because you buy a ticket and the number goes up.
53
Spending them is the hard half.
54
You pay part with points and part with a card, then you ask for a refund, and where do the points go?
55
That's half a test plan on its own.
56
She's right.
57
And earning already happens on the server when you pay, so the app only has to show the balance.
58
So double points would still work if it's the server that counts them?
59
Yeah, it would.
60
The server knows the ticket was bought in the app, so it can double the points right there, and the app just shows the new number.
61
Hmm, let me think about how that sounds to a member.
62
You earn double points in the app and you spend them on the website for now.
63
I can sell that.
64
I don't love it, but I can sell it.
65
And I want to add one thing to the list.
66
The ticket has to open with no signal because half our theaters are in malls and two of them are basically underground.
67
If you're at the door and the app is still loading your ticket, that's a line of annoyed people behind you.
68
That's a must no discussion.
69
So let me say the scope back.
70
In, we have what's playing, picking seats, paying, tickets that open with no signal, and your points balance.
71
Out for now, spending points and snack orders.
72
That's the scope.
73
I'll put it on the project page today with the outlist right next to it so nobody adds things back quietly.
74
Including you?
75
Especially me.
76
Now the date.
77
Mike, you've been holding that face since the first slide.
78
Go ahead.
79
Thanks.
80
Alex, I have to be honest, that date worries me.
81
It's 16 weeks on the calendar, but the holidays at the end of December take two of them.
82
And the last two aren't ours, because by then, the app has to be with Apple and Google.
83
Two weeks for a review?
84
I thought that took a day or two.
85
The review does, usually.
86
It's the rejection that takes the time.
87
A first app often gets sent back for something small, like a privacy question we answered wrong, or a login the reviewer can't get past.
88
Then you fix it, you send it again, and you wait again.
89
So the reviewer needs a test account that can buy a ticket without a real card.
90
Right.
91
So it's 12 weeks of real building.
92
And I'm the only one in this room who's shipped a mobile app before.
93
I hear you.
94
But the festival isn't going to move for us.
95
So what are you asking me for?
96
A different date?
97
Because I can't give you that.
98
Then let's not argue about the date.
99
The date's fixed and the team's fixed.
100
So the only thing left that can move is scope.
101
What I don't want is to find that out in week 13.
102
I want to find out early.
103
How early?
104
Week 4.
105
That's the last week before the holidays.
106
By then, one phone buys one ticket in the test environment, from start to finish.
107
It can be ugly.
108
But it goes through login, the seat map, and the payment, because those are the three parts that could surprise us.
109
I can live with that.
110
If it works in week 4, I'll stop worrying about March.
111
Mostly.
112
And if it doesn't work?
113
Then we cut
114
Scope in the first week of January, while there's still time to cut.
115
And I'm in the room when that happens.
116
You're the one who decides what gets cut.
117
We just tell you what each thing costs.
118
Fair.
119
What comes after week 4?
120
Milestone 2, the end of week 10.
121
Everything in Scope works, and the app goes out to about 50 people inside the company.
122
Then, milestone three is the end of week 14, when both apps go to the stores.
123
That leaves two weeks before opening night for whatever comes back.
124
So, week four, week 10, week 14, and March 19th.
125
I can show that to marketing.
126
Actually, it's better than what I had, which was one date and a lot of hope.
127
Next, who owns what?
128
Ethan, do you want to take this part?
129
Sure.
130
One thing first, because it changes who can do what.
131
I'd like to build the app in React Native.
132
Mike and Thea write
133
React every day on the website, and we get iPhone and Android out of one code base.
134
With one honest warning.
135
It's one code base, but it's still two platforms to test.
136
Thank you.
137
And I have exactly one test phone, and it's my own.
138
I need at least four.
139
A new iPhone and an old one, a new Android and a cheap one with a small screen.
140
Send me the list today.
141
That's a cheap problem. So, owners.
142
Mike, you're the only one who's done this before, so I'd like you to lead the app.
143
Sure, and the seat map's mine, since I'm the one who's scared of it.
144
I'll take the server side and the payment, and I'm the one who talks to the login team.
145
Sarah has the test plan and the phones.
146
Alex, the store pages are yours, with the screenshots, the descriptions, and the privacy answers.
147
And Thea, I'd like you to own the ticket screen.
148
That's the list of your tickets, the code they scan at the door, and making it all open with no signal.
149
Me?
150
I mean, yeah, I'd love to.
151
I should say, I've never built anything for a phone.
152
I've only.. well, I've done the tutorial.
153
Twice.
154
But I've never shipped one.
155
That's fine.
156
It's React, so you already know most of it.
157
And the part that's new, saving the ticket on the phone, we'll build the first version together.
158
Then yeah, the ticket screen is mine.
159
Sorry, quick question though.
160
While we're all building this, who looks after the website?
161
Bugs don't stop for 16 weeks.
162
Nobody put that on the agenda, and somebody should have.
163
Bugs on the website still get fixed, and we take turns, one person a week.
164
But no new features on the website until the app ships.
165
Hmm, the theater managers aren't going to love that.
166
And I need one exception, because the festival page has to go up in February.
167
Everything else can wait, and I'll tell them myself.
168
One page, fine.
169
Last thing on how we work.
170
Questions go in the project channel, not in direct messages, so everyone sees the answer.
171
And every Thursday, for 30 minutes, we look at the app on a real phone.
172
The last big one.
173
What could go wrong?
174
I'd rather hear it today than in February.
175
The seat map.
176
On the website, it's one big drawing of the room, and you click a seat with a mouse.
177
On a phone, a seat is smaller than your thumb.
178
I don't know yet if we can reuse it or have to redraw it from scratch, and those are very different amounts of work.
179
How long to find out?
180
Give me a week.
181
I'll put the map of our biggest room on a real phone and see how bad it is.
182
Good.
183
Mine is login.
184
The website keeps you signed in with a cookie in the browser.
185
The app isn't a browser, so it needs tokens it can keep on the phone.
186
And that part belongs to the login team, not to us.
187
If they can't give us that by week three, Milestone One is in trouble.
188
I'll ask them today.
189
Here's mine.
190
Today, everybody picks up a paper ticket at the counter, even if they bought it on a phone.
191
So has anyone checked that the scanners at the doors can read a phone screen?
192
A dark one or a cracked one?
193
I...
194
Don't know.
195
I assume they could.
196
Then I'll find out.
197
I'll take a phone to the theater downtown and try every scanner they have, with the brightness up and with it down.
198
So you're going to the movies. For work. For work.
199
And I'm expensing the popcorn.
200
Approved.
201
That's the fastest approval I've ever given.
202
Can I add one since it's my screen now?
203
If the ticket's saved on the phone and somebody gets a refund on the website,
204
the phone still shows the old ticket and it still looks fine.
205
Good catch!
206
The scanner checks with the server, so it won't let them in.
207
But they'll be standing at the door with a ticket that looks real.
208
So the app checks again whenever it's online and it shows when it last checked.
209
Thea, that one's yours.
210
Oh, wait, one more thing.
211
Who owns the accounts for the app stores?
212
Does the company even have them?
213
Because for a company, Apple wants to check that the business is real, and I've seen that take two weeks.
214
I have no idea whether we have them.
215
That one's mine, and I'll start on it today.
216
So that's five risks, and every one of them has an owner.
217
We're almost at time.
218
Let me read it back and stop me if I get it wrong.
219
We're building a mobile app for March 19th.
220
The scope is on the project page today and spending points and snack orders wait.
221
Right.
222
Three milestones at week four, week 10, and week 14.
223
If week four goes badly, we cut scope in the first week of January and I make the call.
224
Does everybody know their first job?
225
The seat map.
226
The login team.
227
The movies and a list of phones.
228
Setting up the project with Mike and then the tickets screen.
229
I've got the store accounts and the theater managers.
230
Now the question I really care about.
231
Does anybody have a doubt they haven't said out loud?
232
Because today is the cheapest day to say it.
233
Not a doubt.
234
But I want it on the project page that testing starts with the first build, not in week 10.
235
Written down.
236
It'll be there today day.
237
I said mine already.
238
Ask me again in week four.
239
No doubts from me, but I do have a name for the channel.
240
Popcorn.
241
Project Popcorn.
242
Sold.
243
Project Popcorn it is.
244
Thanks everyone.
245
See you Thursday with a phone.
246
Thanks for listening.
247
What's the first question you'd ask at a project kickoff?
248
Tell us in the comments.
249
All right

앱 다운로드

유창하게 말하는 데 필요한 모든 것

AI 발음 평가문장마다 점수 확인
IPA 발음 연습모든 소리 마스터
단어 학습나만의 단어장 만들기
단어 게임놀면서 외우기

같은 채널

FOR YOU

추천 영상

이 레슨의 어휘와 말하기 포인트

이 말하기 레슨은 영상 “English for Developers: Project Kickoff Meeting”을(를) 바탕으로 합니다. 가장 자주 반복되는 단어는 다음과 같습니다: app, ticket, points, website, seat. 이 영상에는 섀도잉할 문장 249개와 단어 2197개가 있습니다. 말하는 구간의 길이는 12:41입니다. 화자는 분당 약 173단어로, 일상 대화에 가까운 자연스러운 속도로 말합니다. 단어의 87%가 영어에서 가장 많이 쓰이는 3,000단어에 속해 어휘가 쉬운 편입니다.

이 영상의 핵심 어휘

영상에 나오는 익혀 둘 만한 단어 15개를 발음, 뜻과 함께 정리했습니다.

단어발음뜻
theater 명사/ˈθi(ə)tɚ/극장
server 명사/ˈsɝvɚ/서버, 봉사기
slide 명사/ˈslaɪ̯d/미끄럼틀, 미끄럼대
snack 명사/snæk/간단한 식사, 경식
earn 동사/ɝn/벌다
popcorn 명사/ˈpɑp.kɔɹn/팝콘
scanner 명사/ˈskænə/스캐너
privacy 명사/ˈpɹaɪ.və.si/사생활, 프라이버시
laptop 명사/ˈlæp.tɑp/노트북, 랩톱
bug 명사/bʌɡ/벌레
refund 명사/ɹɪˈfʌnd/환불금, 환불
argue 동사/ˈɑɹ.ɡju/논하다, 의논하다
badly 부사/ˈbæd.li/나쁘게, 서투르게
ugly 형용사/ˈʌɡli/추악하다, 못생기다
crack 명사/kɹæk/틈

영상에 나오는 구동사

단어뜻
come back 동사돌아오다
give up 동사항복하다
go up 동사올라가다
pick up 동사줍다
write down 동사적다, 적어 두다

따라 말해 볼 만한 문장

영상에 나오는 짧고 완결된 문장으로, 일상 대화에서 그대로 쓸 수 있습니다:

  • Can I start at the bottom?
  • Ethan, do you want to take this part?
  • While we're all building this, who looks after the website?
  • Can I add one since it's my screen now?
  • What's the first question you'd ask at a project kickoff?

이 영상의 문법

화자가 가장 많이 쓰는 문형을 영상 속 실제 표현과 함께 정리했습니다.

문형영상 속 표현
현재완료 have/has + 과거분사 — 과거의 일이 지금도 관련이 있을 때Have you ever sat · has booked · I've never built
수동태 be + 과거분사 — 누가 하는지보다 무슨 일이 일어나는지에 초점are bought · is called · was bought
관계절 who / which + 절 — 사람이나 사물에 대한 추가 정보one who decides · had, which was · one who talks

주의할 발음

화자는 I'll, I'm, I've 같은 축약형과 약화된 형태를 62번 사용합니다. 들리는 대로 짧게 발음하세요.

  • “th” 소리: theater /ˈθi(ə)tɚ/, thumb /ˈθʌm/
  • “sh”와 “zh” 소리: exception /əkˈsɛpʃən/, precision /pɹɪˈsɪʒ.ən/, rejection /ɹɪˈd͡ʒɛkʃən/, screenshot /ˈskriːn.ʃɑt/

한국어 화자가 어려워하는 소리:

  • /f/ — ㅍ(/p/)으로 바꾸지 말고 윗니를 아랫입술에 대기: refund /ɹɪˈfʌnd/, leaf /lif/
  • /v/ — ㅂ(/b/)과 구별하기: server /ˈsɝvɚ/, privacy /ˈpɹaɪ.və.si/, developer /dɪˈvɛləpɚ/, approve /əˈpɹuːv/
  • /z/ — ㅈ이 아니라 성대를 울리는 /s/: browser /ˈbɹaʊ.zəɹ/, zoom /zuːm/

이 영상으로 연습하는 방법

  1. 먼저 말하지 않고 영상을 끝까지 듣고 모르는 단어를 적어 둡니다.
  2. 0.75배속으로 한 문장씩 섀도잉을 시작하고, 익숙해지면 보통 속도로 돌아갑니다.
  3. 자신의 목소리를 녹음해 원본과 비교하고, theater, server, slide 같은 단어에 특히 주의합니다.

쉐도잉이란? 영어 실력을 빠르게 키우는 과학적 방법

쉐도잉(Shadowing)은 원래 전문 통역사 훈련을 위해 개발된 언어 학습 기법으로, 다언어 학자인 Dr. Alexander Arguelles에 의해 대중화된 방법입니다. 핵심 원리는 간단하지만 매우 강력합니다: 원어민의 영어를 들으면서 1~2초의 짧은 지연으로 즉시 소리 내어 따라 말하는 것——마치 '그림자(shadow)'처럼 화자를 따라가는 것입니다. 문법 공부나 수동적인 청취와 달리, 쉐도잉은 뇌와 입 근육이 동시에 실시간으로 영어를 처리하고 재현하도록 훈련합니다. 연구에 따르면 이 방법은 발음 정확도, 억양, 리듬, 연음, 청취력, 말하기 유창성을 크게 향상시킵니다. IELTS 스피킹 준비와 자연스러운 영어 소통을 원하는 분들에게 특히 효과적입니다.

섀도잉 방법: 단계별 전체 가이드 읽기 →