تدريب Shadowing: CI/CD Explained in 5 Minutes - تعلم التحدث بالإنجليزية عبر الفيديو

جارٍ إنشاء الدرس...
1
Give me five minutes and I'll show you how code gets from a laptop to production environment for millions of users.
2
A developer writes some code on their laptop.
3
A few hours later, that exact code is running for millions of people around the world.
4
And imagine a human barely touched it along the way.
5
Let me show you that journey because it is one of the most satisfying things in all of engineering.
6
Now let's start with the old way.
7
So the modern one makes sense immediately.
8
A developer finishes their code, copies the files onto the live server by hand, restarts it, and hopes nothing breaks.
9
If something is wrong, the website goes down and everyone panics to fix it under pressure.
10
It's slow, it's stressful, risky, and it's easy to make mistakes that takes the whole site offline.
11
The modern way, the exact opposite of this,
12
uses a pipeline to replace the old do it manually and hope for the best way.
13
So think of a pipeline like an assembly line for code.
14
And let's walk through the stations of that assembly line one by one.
15
Step one, developer pushes their code to a shared place like GitHub and pushing that code is the only manual step.
16
Everything after this is automatic.
17
Step two, that push automatically triggers tests.
18
So the pipeline runs hundreds of checks.
19
Does the new code work?
20
Did it break something that used to work before?
21
If any test fails, the code changes are rejected right away before it ever gets near a real user.
22
So this is your safety net.
23
Step three, if the tests pass, the code is packaged into a container image.
24
That sealed box with the application and everything application needs packaged inside of it.
25
So it runs the same way no matter where it lands.
26
Step four, the package is sent first to a staging environment.
27
So staging is a copy of the real environment,
28
like a simulation basically, where where the team can see exactly how the application changes will behave on real environment.
29
Your actual users never see staging.
30
This is for testing or preparing for the actual environment.
31
Step five, if tests on staging environments look good, the package then goes to production,
32
which is the real environment your users actually see.
33
Now, obviously there is already a previous version of the application running on production.
34
So the old version needs to be stopped and the new version deployed.
35
But here's an interesting point.
36
Smart teams do not just flip to the new version for everyone at once.
37
They release it to 10% of users first.
38
So 90% of users still get the old version.
39
Only 10% see the new one.
40
Why?
41
Because you can't possibly test everything before, no matter how careful you are and how many stages you have before.
42
So if something still slipped through the tests, and if anything breaks, only 10% of users will be affected,
43
not 100% of them.
44
And you can roll it back immediately to the previous version.
45
So this allows teams to observe the new version carefully, maybe for a few hours.
46
If everything looks fine, then roll it out to everyone else.
47
Now the names.
48
This whole assembly line is called CI-CD.
49
CI is the automatic testing every time the code changes.
50
CD is the automatic delivery of of those code changes to the users.
51
And together they turn a scary manual all-hands event into this repeatable boring process.
52
And boring is exactly what you want when millions of people use your app actively.
53
You want predictable outcomes without any surprises.
54
So the journey is push, test, package, staging, production.
55
Happening automatically many times a day with a safety net at every step with automated tests
56
and an undo button at the end.
57
Building that pipeline is actually a huge part of what DevOps engineers do
58
and it is the reason companies can ship updates constantly without causing a mess for their entire set of users.

المفردات وملاحظات التحدث لهذا الدرس

يحتوي هذا الفيديو على 58 جملة و668 كلمة للتدرب على الترديد. مدة الكلام 4:52. يتكلم المتحدث بسرعة ثابتة، نحو 137 كلمة في الدقيقة، وهي سرعة مريحة للترديد. 85% من الكلمات ضمن أكثر 3,000 كلمة شيوعًا في الإنجليزية، ويُستحسن مراجعة الباقي قبل البدء.

أهم المفردات في هذا الفيديو

15 كلمة من الفيديو تستحق التعلّم، مع النطق والمعنى:

الكلمةالنطقالمعنى
package اسم/ˈpæk.ɪd͡ʒ/صُرَّة, طَرْد
pipeline اسم/ˈpaɪpˌlaɪn/خَطّ أَنَابِيب
automatic صفة/ˌɔː.təˈmæt.ɪk/تِلْقَائِيّ, أُوتُوماتِيكِيّ
manual اسم/ˈmæn.j(u)əl/كُتَيِّب, كُتَيِّب التَّشْغِيل
laptop اسم/ˈlæp.tɑp/كَمْبْيُوتِر مَحْمُول, حَاسُوب مَحْمُول
bore فعل/boɹ/أَمَلَّ
carefully ظرف/ˈkɛɹf(ə)li/بِعِنَايَة
server اسم/ˈsɝvɚ/خَادُوم m or خَادِم, مُلَقِّم
scary صفة/ˈskɛə.ɹi/مُجَفِّل
seal اسم/siːl/خَتْم
slip فعل/ˈslɪp/اِنْزَلَقَ
panic اسم/ˈpænɪk/ذُعْر, رُعْب
trigger اسم/ˈtɹɪɡɚ/زِنَاد
actively ظرف/ˈæktɪvli/بِنَشَاطٍ
flip فعل/flɪp/قَلَبَ

الأفعال المركبة التي ستسمعها

الكلمةالمعنى
go down فعلنَزَلَ

نطق يحتاج إلى انتباه

  • الكلمات الطويلة — انتبه لموضع النبر: automatic /ˌɔː.təˈmæt.ɪk/, developer /dɪˈvɛləpɚ/, predictable /pɹəˈdɪktəbləl/, manually /ˈmænj(u)əliː/, repeatable /ɹɪˈpiːtəbəl/

كيف تتدرب بهذا الفيديو

  1. استمع إلى الفيديو كاملًا مرة واحدة دون أن تتكلم، ودوّن الكلمات التي لا تعرفها.
  2. ردّد جملة جملة بالسرعة العادية، وكرّر كل جملة حتى يتطابق إيقاعك مع المتحدث.
  3. سجّل صوتك وقارنه بالأصل، مع الانتباه إلى كلمات مثل package, pipeline, automatic.

ما هي تقنية التظليل الصوتي؟

التظليل الصوتي (Shadowing) تقنية تعلم لغة مدعومة علمياً، طُورت أصلاً لتدريب المترجمين الفوريين المحترفين. الطريقة بسيطة لكنها قوية: تستمع لصوت إنجليزي أصلي وتكرره فوراً بصوت عالٍ — كظل يتبع المتحدث بتأخير 1-2 ثانية. تُظهر الأبحاث تحسناً كبيراً في دقة النطق والتنغيم والإيقاع وربط الأصوات والاستماع والطلاقة.

تقنية الشادوينغ: اقرأ الدليل الكامل خطوة بخطوة →