Shadowing Practice: CI/CD Explained in 5 Minutes - Learn English Speaking with Video
Les maken...
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.
📺 Zelfde Kanaal
C1Redis Crash Course - the What, Why and How to use Redis as your primary database
University StudentsBusiness English+1
C12
What is Docker? Docker container concept explained || Docker Tutorial 1
University StudentsBusiness English+1
B21
Every Networking Concept Explained In 20 Minutes
University StudentsBusiness English+1
C12
Microservices explained - the What, Why and How?
University StudentsBusiness English+1
C12
NGINX Explained - What is Nginx
University StudentsBusiness English+1
C12
Kafka Tutorial for Beginners | Everything you need to get started
University StudentsBusiness English+1
C17
If I would start DevOps from 0 - How would I start and what would I learn
University StudentsWorking Adults
✨ Aanbevolen Video
B29
29 zinnen
Git Explained in 100 Seconds
American Accent, en-USUniversity Students+2
B22
190 zinnen
He’s always wrong
University StudentsBusiness English+2
B21
12 zinnen
How I’d Learn Coding in 2026 (Without Wasting Years)
University StudentsBusiness English+1
B21
364 zinnen
Claude Cowork Tutorial: Build Monthly Reports in Minutes
University StudentsBusiness English+1
B21
132 zinnen
How A Car Engine Works
University StudentsBusiness English+1
C12
43 zinnen
SDLC Vs STLC: Software Development Life Cycle and Software Testing Life Cycle
University StudentsBusiness English+1
![Cloud Providers are changing RAPIDLY [REUPLOAD]](https://img.youtube.com/vi/UVz8_JljpGQ/mqdefault.jpg)
B21
55 zinnen
Cloud Providers are changing RAPIDLY [REUPLOAD]
University StudentsBusiness English+1
B21
321 zinnen
How One of NYC’s Fastest-Growing Startups Scaled to $5 Billion
University StudentsBusiness English+1
C15
106 zinnen
A Career in IT
University StudentsBusiness English+1
B21
106 zinnen
Fable 5 Took Over Unity and Built a Game in a Day
University StudentsBusiness English+1
Over deze les
Wat is de Shadowing-techniek?
Shadowing is een wetenschappelijk onderbouwde taalleermethode die oorspronkelijk is ontwikkeld voor professionele tolkentraining en gepopulariseerd door polyglot Dr. Alexander Arguelles. De methode is eenvoudig maar krachtig: je luistert naar native Engelse audio en herhaalt het onmiddellijk hardop — als een schaduw die de spreker volgt met slechts 1–2 seconden vertraging. In tegenstelling tot passief luisteren of grammaticadrills, dwingt shadowing je hersenen en mondspieren om echte spraakpatronen tegelijkertijd te verwerken en te reproduceren. Onderzoek toont aan dat het de uitspraaknauwkeurigheid, intonatie, ritme, verbonden spraak, luisterbegrip en spreekvaardigheid aanzienlijk verbetert — waardoor het een van de meest effectieve methoden is voor IELTS Speaking-voorbereiding en echte Engelse communicatie.