تدريب Shadowing: English for Developers: Real Daily Stand-up Meeting | Listening Practice - تعلم التحدث بالإنجليزية مع YouTube
C1
From clean code to clear communication,
163 جمل
إذا كانت الجمل قصيرة أو طويلة جدًا، انقر على Edit لتعديلها.
1
From clean code to clear communication,
2
welcome to English Not Null,
3
where you learn to present your work with confidence and precision.
4
Have you ever struggled to explain a complex technical problem during a daily meeting in English?
5
You know the issue, but finding the right words can be tough.
6
In this video, we'll listen to a realistic daily stand-up.
7
Our goal is to pay attention to the specific phrases used to describe challenges.
8
Notice how the developers talk about bugs, blockers, and performance issues.
9
This is the real, everyday language you'll use in your career.
10
Let's jump in.
11
Alright team, let's kick off our daily stand-up.
12
Who wants to start today?
13
I can go first.
14
I've been working on the new authentication service.
15
How's it coming along?
16
Any progress?
17
Yeah, it's going okay.
18
I've got the basic structure set up,
19
but I've run into some issues with token refresh.
20
Sometimes the tokens are expiring before they should.
21
I think I need to dig deeper into our JWT library.
22
Do you need any help with that?
23
I might need to discuss further with Alex's team.
24
He's worked with this library before.
25
Okay.
26
You've cleared up all other information about this ticket, right?
27
I've been waiting for some clarification on the security requirements from the client.
28
I see.
29
Have you talked to Henry about it?
30
He's our point of contact with the client.
31
He was quite busy yesterday, so he couldn't help.
32
Oh, I'm sorry about that, John.
33
I've been swamped with meetings.
34
After this meeting, come to my desk and we'll clarify these issues, okay?
35
Great.
36
Thanks, Henry.
37
John, what's your plan for today?
38
I'll keep working on the token validation logic.
39
Oh, and there's that weird bug with the password reset feature I need to look into.
40
The password reset?
41
What's going on with that?
42
It's.. ugh.
43
Sometimes it doesn't send the reset email.
44
Like, you request a reset and it just.. doesn't work, you know?
45
Hmm, that sounds tricky.
46
Any ideas what's causing it?
47
Not really.
48
I mean, it works fine most of the time.
49
It's just… sometimes it doesn't.
50
I'll debug it and update you later.
51
Alright, keep at it.
52
Let me know if you need any help, okay?
53
Yeah, sure.
54
Oh wait, almost forgot.
55
Has anyone seen the updated database schema?
56
I thought the DBA team was supposed to send it over.
57
I think Mark mentioned something about that in the team chat this morning.
58
Did you check Slack?
59
Oh man, Slack.
60
Why didn't he send an email?
61
I haven't looked at Slack today.
62
I'll check after the stand-up.
63
Sounds good.
64
Anything else you want to bring up?
65
Nah, that's it for me.
66
Alright, thanks John.
67
Evan, what's your status?
68
Yesterday, I was implementing the new UI components for the dashboard and ran into some issues with state management in React.
69
Today, I'll be refactoring the code to use Redux for better state handling.
70
State management issues again.
71
What's happening this time?
72
It seems that sometimes the component states aren't syncing properly.
73
It's causing inconsistencies in the UI,
74
especially when dealing with real-time updates.
75
That sounds concerning.
76
Do you have any leads on the cause?
77
I suspect it might be related to how we're handling asynchronous actions,
78
particularly with our WebSocket connections.
79
When multiple updates come in rapidly,
80
we seem to lose some state changes.
81
That's possible.
82
Have you looked into using middleware like Redux Saga to handle side effects?
83
Yes, I've been researching that.
84
I think implementing Redux Saga might help us manage these complex asynchronous flows better.
85
Have you discussed this with the rest of the front-end team?
86
Not yet.
87
I'm trying to put together a small proof of concept before bringing it up.
88
But I may need their input soon.
89
What about the new UI components?
90
When do you think they'll be ready for review?
91
I'll push the initial version to our staging environment this afternoon?
92
It won't be fully styled yet,
93
but the core functionality should be there.
94
I'm aiming to have it ready for a proper review by tomorrow afternoon.
95
That would be helpful.
96
Even if it's not the final version,
97
it will allow the team to start testing and provide feedback.
98
I'll prioritize getting a testable version out.
99
What else have you been working on?
100
There's an ongoing issue with our bundle size.
101
It's getting pretty large and affecting load times.
102
Right.
103
You mentioned that in our last sprint retrospective.
104
Still working through it?
105
Yes, I've started implementing code splitting and lazy loading for some of our larger components,
106
but we're still seeing longer than ideal load times on slower connections.
107
That's concerning.
108
What's your plan to address it further?
109
I'm looking into using Webpack's tree shaking more aggressively,
110
and potentially moving some of our larger dependencies to be loaded on demand.
111
I'm also considering implementing a service worker for better caching.
112
I'm hoping this will improve the situation,
113
but it's a complex issue.
114
Perhaps we should schedule a separate meeting to dive deeper into this,
115
maybe involve some of the performance optimization experts from other teams?
116
That's a good idea.
117
I'll put together some data and we can set that up later this week.
118
Perfect.
119
QA team, what's your status?
120
We've been running our automated test suite against the latest build.
121
we've uncovered a few edge cases in the user profile update flow anything critical nothing shows stopping
122
but there's an intermittent bug where profile pictures sometimes don't update immediately.
123
I'll send over the full report this afternoon.
124
Hmm, that might be related to the state management issues I mentioned.
125
I'll take a look once I get your report, Mia.
126
Sounds good.
127
Oh, and we've started setting up some new end-to-end tests for the dashboard feature.
128
Should have those ready for review by tomorrow.
129
Great work, everyone.
130
Product owner, any updates from your end?
131
Yes, just a couple of things.
132
I've been reviewing the user stories for our next sprint.
133
We might need to adjust some priorities.
134
What's changing?
135
Well, the client's been pushing for that data export feature.
136
They're saying it's becoming crucial for some of their enterprise customers.
137
Oof, that's going to be tricky to implement with our current architecture.
138
We might need to rethink how we're handling large data sets on the client side.
139
Yeah, and we'll need to optimize our API endpoints to handle potentially large data exports.
140
Might impact our current API design.
141
I know it's not ideal timing,
142
but it's coming from the executive level.
143
Can we discuss this more in sprint planning later today?
144
Definitely.
145
We'll need to weigh this against our current commitments.
146
Anything else before we wrap up?
147
Just a quick one.
148
Are we still on for that team building activity next week?
149
You know, the escape room challenge?
150
Absolutely!
151
It's booked for next Thursday afternoon.
152
Sounds fun.
153
Looking forward to it.
154
Alright, that wraps up our daily stand-up.
155
Thanks everyone.
156
Let's have a productive day.
157
That's it for our video today.
158
I hope this has been helpful.
159
Now, I have a question for you.
160
What is the most challenging phrase you've had to say during a daily meeting in English?
161
Leave a comment below and we can all learn from each other.
162
If you found this video valuable,
163
please hit the like button and subscribe to English Not Noel so you don't miss our next video.
تنزيل التطبيق
تقييم بالذكاء الاصطناعي لكل جملة تنطقها
TRENDING
الأكثر شعبية
لماذا تمارس التحدث مع هذا الفيديو؟
إن ممارسة المحادثة الإنجليزية باستخدام هذا الفيديو تعزز من مهاراتك التحدثية في بيئات العمل الحقيقية. على سبيل المثال، الاجتماعات اليومية التي يعقدها المطورون تمثل سياقًا واقعيًا حيث تُستخدم لغة تقنية دقيقة. بمتابعتك لهذا الفيديو، ستتعلم كيفية التعبير عن التحديات التقنية التي تواجهها، مما يمنحك الثقة لتقديم مشروعك بوضوح ودقة. سوف تكتشف كيف يتم استخدام المفردات والتعابير في المحادثات اليومية، مما يساهم في رفع مستوى لغتك الإنجليزية.
القواعد والتعبيرات في السياق
- تعبيرات التقدم: عبارات مثل "I've been working on" تُستخدم لوصف المشاريع الحالية، مما يظهر للآخرين ما تخصه من جهود.
- وصف المشكلات: العبارات مثل "I've run into some issues" و"not really" تعبر عن التحديات التي تواجهها أثناء العمل.
- طلب المساعدة: استخدام "Do you need any help with that?" يظهر أهمية التعاون بين الزملاء عند مواجهة صعوبات.
يمكنك استخدام هذه التعبيرات لتعزيز مهارات ممارسة المحادثة الإنجليزية والتفاعل مع الزملاء في مجال البرمجة والتكنولوجيا.
فخاخ النطق الشائعة
عند الاستماع إلى الفيديو، قد تجد بعض الكلمات أو العبارات التي يصعب نطقها بشكل صحيح، مثل "token refresh" و"authentication service". من المهم ممارسة النطق بشكل دقيق لتجنب التباس المفاهيم. بالإضافة إلى ذلك، انتبه إلى كيفية نطق المطورين لمفردات مثل "reset email" و"password reset". هذا سيساعدك على تحسين طريقة التظليل في الإنجليزية والتحدث بشكل أكثر سلاسة ووضوحًا.
لذا، استخدم هذه الفرصة لتعلم الإنجليزية مع يوتيوب من خلال ممارسة المحادثة الإنجليزية وتطوير مهاراتك في اللغة، مما يفتح أمامك آفاقًا جديدة في مجال العمل.
ما هي تقنية التظليل الصوتي؟
التظليل الصوتي (Shadowing) تقنية تعلم لغة مدعومة علمياً، طُورت أصلاً لتدريب المترجمين الفوريين المحترفين. الطريقة بسيطة لكنها قوية: تستمع لصوت إنجليزي أصلي وتكرره فوراً بصوت عالٍ — كظل يتبع المتحدث بتأخير 1-2 ثانية. تُظهر الأبحاث تحسناً كبيراً في دقة النطق والتنغيم والإيقاع وربط الأصوات والاستماع والطلاقة.
☕ اشترِ لنا قهوة
يظل ShadowingEnglish مجانيًا بنسبة 100% بفضل دعمكم. تكاليف الخوادم والذكاء الاصطناعي مرتفعة — قهوتكم تبقينا مستمرين! 🙏