쉐도잉 연습: 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.
📺 같은 채널
C1Redis Crash Course - the What, Why and How to use Redis as your primary database
Business EnglishUniversity StudentsWorking Adults
C12
What is Docker? Docker container concept explained || Docker Tutorial 1
Business EnglishUniversity StudentsWorking Adults
B21
Every Networking Concept Explained In 20 Minutes
Business EnglishUniversity StudentsWorking Adults
C12
Microservices explained - the What, Why and How?
Business EnglishUniversity StudentsWorking Adults
C12
NGINX Explained - What is Nginx
Business EnglishUniversity StudentsWorking Adults
C12
Kafka Tutorial for Beginners | Everything you need to get started
Business EnglishUniversity StudentsWorking Adults
C17
If I would start DevOps from 0 - How would I start and what would I learn
University StudentsWorking Adults
✨ 추천 영상
B29
29 문장
Git Explained in 100 Seconds
American AccentBusiness EnglishUniversity StudentsWorking Adults
B22
190 문장
He’s always wrong
Business EnglishDaily ConversationUniversity Students
B21
12 문장
How I’d Learn Coding in 2026 (Without Wasting Years)
Business EnglishUniversity StudentsWorking Adults
B21
364 문장
Claude Cowork Tutorial: Build Monthly Reports in Minutes
Business EnglishUniversity StudentsWorking Adults
B21
132 문장
How A Car Engine Works
Business EnglishUniversity StudentsWorking Adults
C12
43 문장
SDLC Vs STLC: Software Development Life Cycle and Software Testing Life Cycle
Business EnglishUniversity StudentsWorking Adults
![Cloud Providers are changing RAPIDLY [REUPLOAD]](https://img.youtube.com/vi/UVz8_JljpGQ/mqdefault.jpg)
B21
55 문장
Cloud Providers are changing RAPIDLY [REUPLOAD]
Business EnglishUniversity StudentsWorking Adults
B21
321 문장
How One of NYC’s Fastest-Growing Startups Scaled to $5 Billion
Business EnglishUniversity StudentsWorking Adults
C15
106 문장
A Career in IT
Business EnglishUniversity StudentsWorking Adults
B21
106 문장
Fable 5 Took Over Unity and Built a Game in a Day
Business EnglishUniversity StudentsWorking Adults
이 레슨의 어휘와 말하기 포인트
이 영상에는 섀도잉할 문장 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/ | 노트북, 랩톱 |
| carefully 부사 | /ˈkɛɹf(ə)li/ | 주의하여, 조심스럽게 |
| server 명사 | /ˈsɝvɚ/ | 서버, 봉사기 |
| scary 형용사 | /ˈskɛə.ɹi/ | 공포의, 무섭다 |
| seal 명사 | /siːl/ | 인장 |
| slip 동사 | /ˈslɪp/ | 미끄러지다 |
| panic 명사 | /ˈpænɪk/ | 공황, 패닉 |
| trigger 명사 | /ˈtɹɪɡɚ/ | 방아쇠 |
| observe 동사 | /əbˈzɜːv/ | 관찰하다 |
| container 명사 | /kənˈteɪ.nəɹ/ | 그릇, 용기 |
| behave 동사 | /bɪˈheɪv/ | 처신하다, 행동하다 |
영상에 나오는 구동사
| 단어 | 뜻 |
|---|---|
| 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/
이 영상으로 연습하는 방법
- 먼저 말하지 않고 영상을 끝까지 듣고 모르는 단어를 적어 둡니다.
- 보통 속도로 한 문장씩 섀도잉하고, 화자의 리듬과 맞을 때까지 반복합니다.
- 자신의 목소리를 녹음해 원본과 비교하고, package, pipeline, automatic 같은 단어에 특히 주의합니다.
쉐도잉이란? 영어 실력을 빠르게 키우는 과학적 방법
쉐도잉(Shadowing)은 원래 전문 통역사 훈련을 위해 개발된 언어 학습 기법으로, 다언어 학자인 Dr. Alexander Arguelles에 의해 대중화된 방법입니다. 핵심 원리는 간단하지만 매우 강력합니다: 원어민의 영어를 들으면서 1~2초의 짧은 지연으로 즉시 소리 내어 따라 말하는 것——마치 '그림자(shadow)'처럼 화자를 따라가는 것입니다. 문법 공부나 수동적인 청취와 달리, 쉐도잉은 뇌와 입 근육이 동시에 실시간으로 영어를 처리하고 재현하도록 훈련합니다. 연구에 따르면 이 방법은 발음 정확도, 억양, 리듬, 연음, 청취력, 말하기 유창성을 크게 향상시킵니다. IELTS 스피킹 준비와 자연스러운 영어 소통을 원하는 분들에게 특히 효과적입니다.