Shadowing Practice: Sec Growth DataScience staff meeting Sep 14 2022 - Learn English Speaking with Video
Bir pratik modu seçin
Her mod tam ekran bir pratik odası açar.
398 cümleler
Cümleler çok kısa veya çok uzun ise, ayarlamak için Düzenle'ye tıklayın.
1
So it is the SEC, meaning secure and govern, growth and data science, meaning applied ML, ML ops,
2
and anti -abuse team meeting.
3
That's a big mouthful.
4
We might get a better name over time.
5
And that's our meeting for September 14th or 15th in APAC.
6
And hi, Alan.
7
Glad you're here why are you here
8
when it's midnight we can talk uh glad you're here don't make
9
it happen to come to this meeting since it's really late for you uh
10
and so but i'm glad thanks for coming at least once
11
so um news and events uh i've got a lot of things on the agenda today
12
because of some of this uh so apologies for that
13
but i think it's going to go down over time based on feedback
14
I'm going to work to do more summarized communications to improve
15
the signal to noise ratio in my communications to groups of people, including this group of people.
16
This was wrote in for this group, adding more items to our staff meeting agenda, often as read -only, rather than posting to our Slack channel.
17
And I am going to be assuming
18
that people leaders on the team will attend this meeting or read the notes and not rely on the Slack channel.
19
So keep that in mind.
20
Let's see.
21
B is a read -only item, unless anybody wants to discuss it. and see Phil has.
22
Hi, welcome Alan to the meeting.
23
I've asked Alan to step in as acting full stack manager for security policies while I hire an EM.
24
Alan has graciously accepted this wonderful opportunity.
25
So welcome, Alan.
26
Thank you.
27
I've got the next item as well.
28
So anti -abuse is moving product sections from SEC to data science.
29
Data science is effectively a rename of the model ops section.
30
So data science will include two stages.
31
The existing model ops, which has three groups in it, which Mom can talk more about.
32
And the anti -abuse stage, which only currently has one group, which is called anti -abuse.
33
I think at some point there are plans to split anti -abuse into two groups, but that's not in the near two.
34
And we're working through all the changes around that.
35
There's lots of workday changes, lots of handbook changes.
36
Mon, did you want to say anything more about data science or model ops?
37
No, I think for us we just roll up to data science.
38
Everything else stays the same.
39
We still have the two main groups, applied ML, ML Ops, and then later
40
Data Ops as part of it, yeah. So,
41
Inee, thanks, Thomas, for continuing to compile and report across all of my teams
42
that I'm responsible for in the engineering allocation meeting on error budgets and reliability and security incidents.
43
So, really do appreciate that.
44
Got to give Neil a high five, too.
45
He does half of these now.
46
And apologies for the noise
47
if I keep asking for what's the story behind what's going on with reliability or error budget stuff.
48
Just trying to provide air cover. And apologies, Neil.
49
I totally forgot you took half of these since Thomas has been doing it for so long.
50
But I appreciate it, Neil.
51
I know you volunteered for it and we discussed it, but I just forgot.
52
Kind of a thankless role, honestly.
53
And I volunteered because of the exposure I get from it.
54
It's nice to be part of a different collective group of people.
55
I was going to mention, I'll type this in here, but Tiago had set up for container security a bot that weekly,
56
I think it's Mondays or like Sunday, will ping the team and ask for a volunteer to go and resource that data.
57
And we just enabled it for Threat Insights.
58
It's actually pretty sweet and it does all the work for you, Thomas.
59
Right?
60
We don't have to ping people ourselves.
61
So I'll put a note in there for that.
62
Pete, F is read only, and Bill, you've got G.
63
Yeah, talent assessment.
64
So we had an update from Juliana.
65
The dates haven't been confirmed yet, but it'll be sometime from mid -October through to December.
66
I think eGroup sign -off is expected to be mid -December before everyone goes on holiday.
67
They've got a draft timeline in there, but the dates aren't in the handbook yet.
68
The big change is we're moving to do it in Workday.
69
That's not available yet.
70
I haven't seen a demo of it.
71
I don't know what.
72
questions will be asked but there's an optional self -evaluation which will move into workday and
73
the work that we do as managers will also happen in workday
74
at the moment some people are using the google doc
75
which is listed on the talent assessment page for self -evaluations
76
and for the manager work i'd suggest continuing to use those docs until we get access to work day
77
and see what the exact differences are.
78
H, I, and J are read only unless anybody wants to discuss them.
79
Thomas, you got item K.
80
Yeah, apologies for the late like live addition to the agenda on this one, but one more note on a change we're rolling out within
81
Secure pretty lightweight and that we're establishing a second team within dynamic analysis um
82
and so uh issue is there for folks want to play
83
that would like to follow along
84
or ask any questions about it um for the plan for right
85
now is i'm going to be serving as a team to acting em
86
and in addition to normally scheduled uh some duties for lack of a better way of putting it
87
and so happy to answer any questions that folks have about that I had a quick question.
88
We've done the same thing in Threat Insights with Neil and Tiago each having teams.
89
What are you going to call your new team or how will you differentiate?
90
Was not planning to differentiate it.
91
It's just a second team within dynamic analysis.
92
We're not creating a new group, which I think is the same pattern that's happening within
93
Threat Insights as well.
94
It's just two teams.
95
I know that there's Tangerine and there's Navy.
96
I'm not a tangerine person myself.
97
So we'll have to figure it out.
98
Yeah, I don't know if there's another tea color, Thomas.
99
I struggled with that one.
100
That's the theme.
101
Tomato.
102
I don't know.
103
We'll figure it out.
104
We'll figure it out.
105
We'll figure it out.
106
The differentiation, I think the difference between what's happening in Threat Insights
107
and within dynamic analysis is that this is a split or long feature category.
108
even though we're keeping that we're not superior new group.
109
It is there's the distinction is along like who's working on specific feature categories themselves.
110
So the the the the where the fracture point is happening is is a little different.
111
But the but the approach and effect are the same.
112
I hope.
113
So on to big rocks and hot issues section.
114
I don't know if it's a big rock, but kind of long here perhaps more than that.
115
So I did
116
that survey where you got an awesome response rate from the team on how to improve the MR rate for the team.
117
And then I took a really long time to go through all the results and summarize and make initial recommendations.
118
So I lost a little bit of momentum.
119
I got caught up in other things like cross -functional prioritization and the customer escalation.
120
So since then, this is actually used by John Hope to lead a discussion
121
at the development offsite last week on just improving engineering velocity is one of the things he used to power it.
122
So it had value there.
123
But I've seen no comments, I think, from anybody in this group, which means either no time forgot about it or it doesn't,
124
we looked at it and it doesn't have much value.
125
And any of those things are okay.
126
I'm just curious where the group landed.
127
And if you haven't taken a look yet to see
128
if there's anything you want to take away from it on things you might want to consider, I'm asking you to do so and to consider,
129
not to do, but to consider.
130
Anybody got a chance to read it yet and think about it or not just yet?
131
My guess is perhaps everybody's really busy and they haven't left yet.
132
I mean at a high level
133
Jay, Neil, Tiago we've talked about changes.
134
I think Jay you've already looked at some changes around refinement
135
that was an area that you were going to look at for anti -abuse
136
and report back by the end of the quarter.
137
Tiago and Neil I can't remember what where we ended up with for threat insights.
138
Yeah I'm hoping that MR rate is kind of an artifact or byproduct of some other actions.
139
The big thing we're doing is more whole type of work, like random miscellaneous, not schedule, not PM necessarily actions or issues.
140
And that actually is creating some more additional work.
141
Like it's just like free time work.
142
I want to change of pace, move to something else momentarily.
143
And these are generally smaller types of issues too.
144
So they're quicker to knock out.
145
Therefore they create more MRs, which has been a cool byproduct.
146
So I think that's helping us succeed there.
147
Yeah, we're also seeing some success with, we've implemented like a weekly refinement meeting,
148
kind of check in, make sure that stories are broken down tiny enough.
149
I think with smaller bits of work, we're seeing a higher MR rate.
150
It's debatable whether or not that's like just inflated, right?
151
Like you can work on a small piece of code
152
and ship it and you can do
153
that a lot of times you're going to get a higher MR rate we're trying to be reasonable with
154
that um I am noticing a nice tick up uh after implementing the refinement meeting so let's hope for the best
155
I was going to say one note on refinements um in static analysis
156
we're experimenting with the new section in our planning feature, which is called looking forward.
157
And in there, we're using that as like a baseline where we add issues
158
that we think need refinement that will most likely be worked on in the next one to three milestones.
159
So we're using that as kind of a base cover for some engineer to go in
160
and add their issues and make sure they get refined within this milestone, not necessarily any implementation, but just refinement itself.
161
I should stop talking on mute.
162
Thank you, Omar.
163
Thomas, you want to verbalize your comment?
164
Yeah, I'll verbalize and then I'll say more
165
and then I'll finish writing what I was going to put down underneath it in just a moment.
166
So this was an agenda item with the EMS
167
and I can say it now in the secure stage since that is the analyzer teams now.
168
So this was a topic yesterday.
169
So I would assume that this is more like I had a chance to read but not digest the content.
170
And what I was about to write, and I am cautious in saying this because it almost comes across as smug,
171
and that is not my intent.
172
In that, looking at the MR rate within SEC compared to company -wide,
173
historically it runs two to three MRs per engineer per month higher.
174
And I think a good bit of that has to do with the, I mean, we've taken this to be true,
175
or at least asserted it to be true in
176
that it's smaller teams that are working closely together in less busy projects than we see within the Rails platform itself,
177
which does have an impact.
178
It's, that's not to say that we cannot do better, but the comparison and the favorable comparison,
179
at least to me, and I will admit this, at times will lessen the urgency on this particular topic.
180
And I have to admit that bias that I have.
181
Thanks, Thomas.
182
Thanks, everyone.
183
So I didn't see any comments on the issue, but that's totally fine.
184
People found some of it useful, some of the analysis useful, and that's great.
185
So I will close the issue accordingly
186
and just link to these notes good stuff thomas
187
you've got item b okay i'll write after this then all right fed ramp
188
and the can't or won't fix security issues
189
that way maybe we may be having there's uh so we've got um uh
190
the for security issues that are subject to fed ramp
191
if we if you have a feature category that is fips compliant
192
or certified you're probably going to be part of the fed ramp evaluation
193
and any security issue that has a CVE associated with it, which means dependency or container scanning specifically, has to have a remediation plan,
194
even if they're false positives.
195
And so that's led to a separate discussion on what do we need to do for,
196
do we need to do anything related to security findings on the commercial versions of analyzers specifically?
197
That was the catalyst for this particular conversation
198
because on container scanning we get a lot of findings related to debian based images
199
that that project has not shipped a fix for or won't fix ship a fix for
200
so there is a separate thread that is going on here about what to do
201
and can we do deviation requests in bulk for this class
202
of for this for this class of um of findings um the the tldr is below.
203
And there's a couple of options that are being brainstormed within this particular thread.
204
So I wanted, and I know I've said a lot of words and I didn't say it well,
205
but I wanted to bring it here in case there was any questions or commentary.
206
Nothing directly related to what you've just talked about, but but sort of related for FedRAMP,
207
you're looking at any FIPS related security issues that have been raised.
208
How far are you going in terms of auditing to find anything that hasn't already been identified?
209
There is, I'll link in another issue, a separate issue
210
that has instructions from AppSec on what they would like us to do as far as setting up container scanning.
211
And they have set up a project with a single configuration that they're asking us to use.
212
There is some debate as to how that project has been configured
213
because it uses a combination of three container scanning tools rather than one.
214
And so they've asked us to use that as a baseline for the FIPS images specifically,
215
since they're UBI or the UBI specific images.
216
they're they're equivalent in my mind even though they're they're they're different meanings
217
so tld out talk to appsec got
218
it nakil nakil george is our stable counterpart of folks don't know at least in sec um
219
and so he's been quite responsive and keen
220
and he is also helping chase down answers when uh
221
when he doesn't have them so uh that's a big uh he's been he's been a big help thus far Yeah.
222
So in, thanks for bringing this up, Thomas.
223
So in the hallway, so from the development staff meeting,
224
I copied and pasted the notes in there,
225
but net is the TLDR is can folks,
226
the request to me and my peers was can folks check with their teams to see if the approvals are affecting them.
227
So this is the new approval rules on segregation of duties.
228
So last this group, not that everybody's here, but in the group and they shouldn't be because all meetings are optional,
229
but has this had an impact, these new approval rules?
230
Anecdotally, I've seen a few cases where team members have realized that they need to get an additional approval,
231
but I'm not aware that it's actually slowing things down.
232
Okay.
233
No news is good news on this probably, unless it's happening and we're not noticing it.
234
We're just slowing things down, but just keep an eye on it in case it does.
235
Everyone, please.
236
It's good stuff.
237
With recent changes, we've done a couple of different changes with secure, govern, broken out from secure,
238
and a data ops team, and this and that.
239
I just compared the name of my team with my peers.
240
My peers have one word team names, ops, dev, create, et cetera.
241
Mine is growth and data science, which is pretty wordy.
242
It also makes sense that when I go into dashboards, I have to pull data from multiple places across my teams.
243
So I was thinking about a one word name.
244
I've started to get feedback on it.
245
Naming things is really important at GitLab to name the right kinds of things and give them good names.
246
So I'm going to run it by David DeSanto tomorrow.
247
He's a great person to bounce such things off of.
248
I landed on enrichment because what we do makes other things better.
249
We enrich them.
250
It's kind of a very broad term, but it does cover what we do.
251
Not sure we're going to change the name, which I'm not sure it's going to affect anyone but me.
252
That's actually my intent is it only affects my stuff,
253
not everyone else's, but at least everyone else's in a small way or others in a small way, but we'll see.
254
Any thoughts on this?
255
Good idea, bad idea?
256
I'm not wed to this, I'm looking for feedback.
257
Yeah, obviously the other examples relate to either sections or stages, whereas enrichment doesn't.
258
So you'd be introducing something new here.
259
This affects me as well.
260
I have a subset of enrichment, so it would be kind of enrichment light?
261
I'm not sure.
262
I'm not sure we'll, I think you and I have spoken about this.
263
I'm not sure we would get approval to introduce a new name or department level.
264
We'd certainly have to talk to people ops about introducing that in Workday.
265
Okay.
266
Okay.
267
So a couple of things, you know, these kinds of things I would sometimes put in Slack,
268
but I'm trying to avoid a number of distinct Slack messages.
269
So putting it in here, making a lot read -only when possible.
270
So I've got C though, which is not read -only.
271
So I would like to add announcements of work anniversaries and new hires to the meeting template.
272
PM does this.
273
I attended the PM staff meeting.
274
I was a guest speaker there this week.
275
And like the camaraderie, we have good camaraderie.
276
The camaraderie there was pretty good.
277
You know, Fern, who's shadowing me today, I think he sat in on the PM meeting as well.
278
It was a pretty good feel of just people really knowing each other well and getting along well.
279
So those are just two things I took away from it, is anniversaries and new hires.
280
I'll verbalize Tiago's comment.
281
Great idea for new hires.
282
Don't care much about work anniversaries.
283
We already have a bot for that.
284
What I'd say is I always seem to miss the bot announcements
285
as they cover the whole company versus Abad just announcing for our team.
286
If no interest in that part, I'm happy to exclude.
287
So Neil, you like the idea of adding such a great anniversary or you don't?
288
I mean, just last week, I think it was Phil celebrated his third year and I congratulated him,
289
but then I missed another team member in SEC.
290
You know, because there's like 20 people on that list.
291
Plus it's team member updates.
292
That's not a channel I look at a lot, like weekly.
293
I just happen to see that the day of.
294
So I do like being able to celebrate together in this group.
295
Maybe also a thanks or praise section.
296
Like, thanks for doing this.
297
Great job on that.
298
To remind ourselves to do that.
299
And as engineers, we tend to focus on the problems and challenges and not the celebrating the wins.
300
Are you suggesting that we add new content into this document for that, or that we just link to the Slack announcements that we've already made.
301
I think it's nice to verbalize them.
302
So maybe link to the Slack announcements, but also verbalize it.
303
I know it sounds like a bunch of busy work.
304
I don't want to do things twice.
305
Maybe we add the sections and people use them as they see fit, whatever that happens to be.
306
But please don't create busy work for yourself either.
307
So judgment call by each person.
308
Thomas, it looks like you had a Thomas and Mon, you had some thoughts on this too.
309
Yeah, I like it.
310
We don't celebrate enough.
311
We don't do enough for team cohesion, team celebration across the board.
312
And just as a corollary related thing that I haven't communicated well,
313
I was hoping to add this kind of thing to our monthly section -wide retrospectives new hires, discretionary bonuses, work anniversaries, big feature releases.
314
I mean, anything that we want to announce and celebrate, we ought to make sure that it's, I don't want to say shout to the rooftops,
315
or shout to the heavens, but they're big deals and we don't make, and we undersell, in my opinion.
316
Yeah.
317
Oh, sorry.
318
And hey, Fernando here.
319
So I'm shadowing Wayne now just to introduce myself.
320
from the technical marketing team.
321
And I'll send the document right now, which is something that we do for our kind of get together team meetings.
322
And it kind of shows you can you can look through it.
323
I shared it to everyone on the Zoom chat, but you can see that we provide updates, the new team members and small little introductions.
324
And you can see sections that we have on gratitude and actual spotlights that we show like who we're actually praising, what they've done that's good,
325
and how we can highlight that because that will motivate employees, kind of really increase that morale because what we're seeing is
326
these employees are actually getting recognized for good work that they've done and they're getting shout outs because a lot of times,
327
at least in our team, the case is we don't really, although we work with each other, we sometimes are kind of siloed,
328
busy working on different things.
329
So it's good to know what everyone's working on and what everyone's doing.
330
So somewhat related to what you were just speaking on, but just thought I'd share that.
331
Thanks, Fernando.
332
In D, so I'm not going to read all of this from Daniel Croft,
333
but summarizing, he is looking for feedback on the development vision and mission and direction.
334
We're brainstorming in the development department.
335
on Mission Envision in particular.
336
The approach is we want everybody to open up a little spreadsheet and follow the instructions, anybody interested.
337
So if you're interested in doing so, it should take about 10 to 15 minutes.
338
Please do it in the next week.
339
Good stuff there.
340
Something we covered also at the development offsite that Daniel took as an action item to follow up on.
341
Thomas, you've got E.
342
Yep.
343
All right.
344
Because I cannot remember.
345
And so I'm hoping to crowdsource a little bit of configuration archaeology, so to speak.
346
Is there a reason that we don't use reviewer roulette? If folks can remember.
347
The reason I'm asking is contained within that thread.
348
But that is a tool that actually is being used to track if we have enough maintainers on any given project.
349
And since we don't use it, we're showing up.
350
and so that's why I was that's why I'm asking
351
when you say reviewer roulette are you talking about on the individual analyzers yeah
352
speaking only for dash we haven't had a need for it because we have
353
six engineers that's just going to roulette the same six people
354
yeah rule a six sided die that's what I kind of think it is but it's
355
from a larger like if the company like where do we need more maintainers is the question that the organization is asking.
356
I mean I'd suggest they're looking in the wrong place if they're looking in roulette
357
to see to find out the number of maintainers
358
that's the wrong place the engineering projects page should list all the maintainers
359
if you set up your team yaml entries correctly I would have thought that was more than single source of truth.
360
apparently not so yeah
361
yeah I'm looking at the chart I mean
362
I think on some of these projects we just haven't filled
363
it out um I'll give you like we have the API um like hub fuzz we have one engineer
364
that works on it uh so we haven't gone
365
and added a maintainer there because they know who they are um
366
so if we trying to maintain
367
that as a single source of truth we need to just go through and scrub it
368
sorry seth i'm reminded
369
i'm reminded of the spider -man meme with the two
370
spider -men pointing at each other who's the reviewer who's the author it's it's the same person
371
it's been it's been a long day so i'm a little punchy so but yes that makes sense
372
so seth are you saying you you haven't added it to individual team members yaml files in the handbook yet.
373
Right.
374
I believe for that one, there's just no entry for it.
375
I mean, we could.
376
I think if you do that, that should do it.
377
Yeah.
378
Well, it should.
379
They shouldn't be using just roulette.
380
They should be using that as a source of trades.
381
And I think if you've listed maintainers, that should cover it.
382
A follow -up question would be, does that cover the senior plus engineers must be a maintainer requirement or not?
383
Thomas, you buried the lead.
384
I took the read only off your comment there so you can announce it.
385
Well, we're going to end with the best news of the day.
386
That's all.
387
But the maintainer requirement, yes, it does.
388
I mean, because it's required for senior plus, going back to that, is just maintaining one or more,
389
I think, is the requirement, if I remember correctly.
390
so i was talking about the olivier news yeah i know
391
i was just making sure we were finished with the topic above all right
392
and we're at time so i will move on and take
393
that as a prompt yeah olivier has uh popped back on slack to announce
394
that the newest edition of their family is here
395
and happened over the weekend uh so uh uh so uh big big congrats to his family for that and uh
396
We'll be hoping to celebrate him later when he returns to work.
397
Google, thanks everybody.
398
Have a great day.
Uygulamayı İndir
Akıcı konuşmak için ihtiyacınız olan her şey
AI TelaffuzHer cümleyi puanla
IPA AlıştırmasıHer sesi ustalaştır
Kelime BilgisiKelime bankanızı oluşturun
Kelime OyunuOynarken öğrenin
Aynı Kanal
C11
2026-05-05 Tufts Capstone project presentation
Daily ConversationUniversity Students
C12
2022-07-25 Analytics Section Meeting
Business EnglishWorking Adults
![[REC] Key Meeting - Engineering (Public Stream)](https://img.youtube.com/vi/qGFoZ8yodc4/mqdefault.jpg)
C19
[REC] Key Meeting - Engineering (Public Stream)
Business EnglishWorking Adults
C1Product Marketing Meeting (weekly) 2021-06-28
Business EnglishUniversity StudentsWorking Adults
FOR YOU
Video Öner
C11
623 cümleler
The Only SaaS Moats Left in 2026
Daily ConversationUniversity StudentsWorking Adults
C11
402 cümleler
Inside a Biotech Company: Roles, Teams & Where You Could Fit In | EP 14
Daily ConversationUniversity StudentsWorking Adults
C11
689 cümleler
Database Sharding! Designing Data-Intensive Applications chapter 6
Daily ConversationUniversity StudentsWorking Adults
C11
364 cümleler
Running AI Agents in Secure Sandboxes with E2B & Docker MCP | Docker’s AI Guide to the Galaxy
Daily ConversationUniversity StudentsWorking Adults
C11
37 cümleler
How Anthropic uses Claude in Product Management
Daily ConversationUniversity StudentsWorking Adults
B28
113 cümleler
Effective Team Meetings - Getting it Right
Business EnglishDaily ConversationUniversity Students
C13
55 cümleler
OpenAI’s lead engineer was secretly a spy...
Daily ConversationUniversity StudentsWorking Adults
C11
207 cümleler
Your AI Agent Starts Every Session Like a New Hire - Killian Carlsen-Phelan, Sonar
Daily ConversationUniversity StudentsWorking Adults
C11
346 cümleler
Trust the Process: How to Design Teams That Actually Work
Daily ConversationUniversity StudentsWorking Adults
C12
499 cümleler
What's New in Zephyr 4.5?
Daily ConversationUniversity StudentsWorking Adults
C12
151 cümleler
We've got separation of concerns wrong
Daily ConversationUniversity StudentsWorking Adults
C138 cümleler
"Dive Deep" Leadership Principle Explained by Amazon CEO Andy Jassy
Daily ConversationUniversity StudentsWorking Adults
Bu dersin kelimeleri ve konuşma notları
Bu konuşma dersi “Sec Growth DataScience staff meeting Sep 14 2022” videosuna dayanıyor. Bu videoda gölgeleme çalışması için 398 cümle ve 4517 kelime var. Konuşma bölümü 28:58 sürüyor. Konuşmacı dakikada yaklaşık 156 kelimeyle, günlük konuşmaya yakın doğal bir hızda konuşuyor. Kelimelerin %83’i İngilizcede en sık kullanılan 3.000 kelime arasında; geri kalanına başlamadan önce bakmakta fayda var.
Bu videodaki önemli kelimeler
Videodan öğrenmeye değer 15 kelime, telaffuzu ve anlamıyla:
| Kelime | Telaffuz | Anlam |
|---|---|---|
| slack sıfat | /slæk/ | gevşek |
| hire fiil | /ˈhaɪɹ/ | kiralamak |
| container isim | /kənˈteɪ.nəɹ/ | kap, konteyner |
| introduce fiil | /ˌɪntɹəˈdus/ | tanıştırmak |
| feedback isim | /ˈfiːdˌbæk/ | geri bildirim |
| announcement isim | /əˈnaʊns.mənt/ | ilan, beyan |
| agenda isim | /əˈd͡ʒɛn.də/ | ajanda |
| apology isim | /əˈpɑ.lə.d͡ʒi/ | itizar, özür |
| enrichment isim | /ɪnˈɹɪt͡ʃ.mənt/ | zenginleşme |
| topic isim | /ˈtɑpɪk/ | mevzu, tema |
| thread isim | /ˈθɹɛd/ | iplik |
| remind fiil | /ɹəˈmaɪnd/ | hatırlatmak, anımsatmak |
| volunteer isim | /ˌvɑlənˈtɪɹ/ | gönüllü |
| requirement isim | /ɹɪˈkwaɪɹmənt/ | gereklilik, zaruret |
| peer isim | /pɪɹ/ | akran, emsâl |
Duyacağınız deyimsel fiiller
| Kelime | Anlam |
|---|---|
| come across fiil | karşıdan karşıya geçmek |
| find out fiil | anlamak, ortaya çıkarmak |
| get along fiil | kardeşçe yaşamak, iyi geçinmek |
| get together fiil | toplanmak, buluşmak |
| roll out fiil | sunmak |
| show up fiil | ortaya çıkmak |
Tekrar etmeye değer cümleler
Videodan, günlük konuşmada yeniden kullanabileceğiniz kısa ve tam cümleler:
- I've got the next item as well.
- We don't have to ping people ourselves.
- I haven't seen a demo of it.
- Thomas, you want to verbalize your comment?
- Is there a reason that we don't use reviewer roulette?
Bu videodaki dil bilgisi
Konuşmacının en çok kullandığı yapılar, videodaki sözcüklerin aynısıyla:
| Yapı | Videoda |
|---|---|
| Present perfect have/has + fiilin üçüncü hâli — geçmişte olan ama şimdi de önemli olan bir eylem | I've asked · has graciously accepted · haven't been confirmed |
| Edilgen yapı be + fiilin üçüncü hâli — kimin yaptığı değil, ne olduğu önemli | is called · is read · been confirmed |
| İlgi cümlecikleri who / which + cümle — bir kişi ya da şey hakkında ek bilgi | ops, which has · group, which is · evaluation which will |
Dikkat edilecek telaffuzlar
Konuşmacı I'm, we're, don't gibi kısaltılmış biçimleri 159 kez kullanıyor. Bunları duyduğunuz gibi kısa söyleyin.
- “th” sesleri: thread /ˈθɹɛd/, underneath /ˌʌndɚˈniθ/
- “sh” ve “zh” sesleri: shout /ʃaʊt/, shadow /ˈʃædəʊ̯/, evaluation /ɪˌvæljuˈeɪʃn̩/, instruction /ɪnˈstɹʌkʃən/, configuration /kənˌfɪɡ.əˈɹeɪ̯.ʃən/
- Uzun kelimeler — vurguyu doğru yere koyun: apology /əˈpɑ.lə.d͡ʒi/, necessarily /ˌnɛs.əˈsɛɹ.ə.li/, evaluation /ɪˌvæljuˈeɪʃn̩/, configuration /kənˌfɪɡ.əˈɹeɪ̯.ʃən/, differentiate /dɪf.əˈɹɛn.ʃi.eɪt/
Türkçe konuşanların zorlandığı sesler:
- /w/ — dudaklar yuvarlak, /v/ değil: requirement /ɹɪˈkwaɪɹmənt/, whereas /(h)wɛɹˈæz/, lightweight /ˈlaɪt.weɪt/, hallway /ˈhɔlˌweɪ/
- Kelime başındaki ünsüz kümesi — araya ünlü eklemeyin: slack /slæk/, scan /skæn/, thread /ˈθɹɛd/, praise /pɹeɪz/, spider /ˈspaɪ̯dɚ/
- /æ/ — “e”den daha açık: slack /slæk/, feedback /ˈfiːdˌbæk/, scan /skæn/, dynamic /daɪˈnæm.ɪk/, handbook /ˈhændˌbʊk/
Bu videoyla nasıl çalışılır
- Videonun tamamını konuşmadan bir kez dinleyin ve bilmediğiniz kelimeleri not edin.
- 0,75× hızla başlayın, cümle cümle tekrar edin ve kolaylaşınca normal hıza dönün.
- Kendinizi kaydedin ve orijinaliyle karşılaştırın; slack, hire, container gibi kelimelere özellikle dikkat edin.
Gölgeleme Tekniği Nedir?
Gölgeleme, başlangıçta profesyonel tercüman eğitimi için geliştirilen ve çok dilli Dr. Alexander Arguelles tarafından popüler hale getirilen, bilim destekli bir dil öğrenme tekniğidir. Yöntem basit ama güçlüdür: ana dili İngilizce olan bir sesi dinler ve hemen yüksek sesle tekrar edersiniz — konuşmacıyı 1-2 saniye gecikmeyle takip eden bir gölge gibi. Pasif dinleme veya dilbilgisi alıştırmalarının aksine, gölgeleme beyninizi ve ağız kaslarınızı gerçek konuşma kalıplarını eşzamanlı olarak işlemeye ve yeniden üretmeye zorlar. Araştırmalar, telaffuz doğruluğu, tonlama, ritim, bağlı konuşma, dinleme anlama ve konuşma akıcılığını önemli ölçüde geliştirdiğini göstermektedir — bu da onu IELTS Konuşma hazırlığı ve gerçek dünya İngilizce iletişimi için en etkili yöntemlerden biri yapar.