쉐도잉 연습: Helpdesk to Sysadmin - 3 Things You Must Learn First - 영상으로 영어 말하기 배우기
연습 모드 선택
각 모드는 전체 화면 연습실로 열립니다.
132 문장
문장이 너무 짧거나 길면 Edit를 눌러 조정하세요.
1
What are three things you must know to move from help desk to sysadmin?
2
My name's Jake.
3
I've been working in IT at an MSP for about a year now,
4
and this is how I was able to break out of tier one and move up to system administrator.
5
For those of you who don't know, an MSP is a managed service provider, so we give IT services to other companies.
6
So the first thing
7
you're going to have to learn in order to move up is how to read logs like a bloodhound.
8
I don't care if it's event viewer, syslogs, show commands, GP result,
9
You have to be able to read logs like your life depends on it because it does.
10
Logs are where the real answer lives.
11
You can look for things like security event logs 4625 failed logons.
12
Don't just look at the username look at these sub status codes and use GPT to make sense of them.
13
This is gonna give you a ton of information.
14
Group policy using things like GP result slash H is super clutch
15
because you can push that HTML file out to a place on the computer
16
and then analyze exactly what policies it's getting and what policies it's not getting.
17
You might see access denied, missing scripts, a GPO not being applied because of some security group.
18
You might use logs to look for DNS issues, bad forwarders, or stale A records.
19
Oftentimes you're going to find these things faster in logs than just pinging around aimlessly.
20
Now why does this matter?
21
Because at level one, you reboot and if it doesn't work, you escalate.
22
You do some basic troubleshooting and you escalate.
23
At the sysadmin level, you're responsible for finding the answer to the problem.
24
Not only do you investigate, you bring receipts.
25
You don't guess, you have to prove it.
26
Now, one of my first wins at sysadmin level was
27
when one of our company's core apps was not performing the way it was supposed to be performing.
28
It was dropping connections and running slow,
29
and I got into one of those very common situations where the vendor and seemingly everybody is blaming the network.
30
I was able to use tools like
31
Continuous Ping and WinMTR to prove that there was no packet loss or any real substantial latency.
32
We pulled performance data, got on multiple vendor calls,
33
rebuilt tunnels, and ultimately was able to work with them to show that it was a CPU bottleneck on their end.
34
This is when people start trusting you with the bigger stuff,
35
when you're able to find data and prove that it is or isn't what you think it is or isn't.
36
The second thing I think
37
you've got to know in order to go up to level
38
two to assist admin is you have to understand DHCP and DNS.
39
I know it sounds boring, but honestly, 90 % of weird IT issues trace back to one of these two things.
40
DNS, how your device actually resolves URLs.
41
So when a user types in portal .office .com, the device doesn't just automatically know where to go.
42
It's going to start by checking its local DNS cache.
43
Then it's going to hit its configured DNS server, usually your domain controller.
44
That's either going to help resolve the name internally or forward it externally to somewhere else.
45
So you need to know the difference between things like forwarders and root hints.
46
When your DNS server doesn't know the answer, where does it ask?
47
You need to know the difference between internal and external zones.
48
Is the name hosted inside your network or outside your network?
49
And then aging
50
and scavenging are going to be super important to things like cleaning up old stale DNS entries
51
because these are going to cause conflicts and issues.
52
And then DHCP is how IPs actually get handed out on a network.
53
Most devices, most of the time are not going to have a static IP set.
54
They're going to have one automatically handed to them by this protocol.
55
Your DHCP server is going to hand them out like a parking lot manager.
56
But if two cars get in the same spot, that's an IP conflict.
57
So you need to know how leases work and when they expire
58
and how they expire because they don't actually expire at the end of the lease.
59
They expire first at the middle of their lease, how to make reservations like for critical devices like printers or servers,
60
and then what causes conflicts like overlapping scopes or someone setting a static IP within a DHCP range.
61
Super duper important, something that we do all the time.
62
Let me give you a couple real world examples.
63
We used to have clients with the DNS server set to the loopback address, which is 127 .0 .0 .1,
64
because the old Cisco umbrella roaming client used this to resolve DNX or really to proxy DNS.
65
This causes all kinds of issues
66
because the umbrella roaming client is no longer a thing and a lot of devices still have that loopback address set statically.
67
So DNS just doesn't work and people say my internet doesn't work and then you have to go in and fix it.
68
I've also time and time again seen printers go offline because they have static IPs within the DHCP range.
69
Random drops and things will print and then they won't print and all these weird behaviors trace back to DHCP.
70
Again this stuff happens all the time.
71
So why does this matter?
72
If a user can't access his shared drive or Outlook keeps going offline
73
when they hop on the VPN or hop off the VPN
74
or a printer won't work sometimes or it only works after a reboot.
75
Probably DNS or DHCP.
76
So again, the help desk resets the nick and hopes for the best.
77
The sysadmin opens the DHCP console, checks the lease, reviews DNS records, and finds the source of the issue.
78
That's the difference.
79
And then finally, something you have to know to go up to sysadmin is scripting and automation.
80
If you're doing something more than twice a day, script it, period.
81
You can start with using PowerShell to create users.
82
And then we can automate report generation, exporting things to CSV.
83
We can use scheduled tasks to loop or batch process changes.
84
And when you're doing all this, absolutely use GPT and VS Code as your personal helpers.
85
We live in an amazing time where you don't have to read a book and actually learn PowerShell.
86
You can ask ChatGPT and it will give you a phenomenal answer most of the time.
87
So I wasn't some coding genius, but I learned early on that I have to use PowerShell to save myself time.
88
And scripting will do this for you.
89
It'll open up an absolute whole new world of productivity.
90
For me, the first time that I really saw this was
91
when I had to remove 20 contractors who were all fired at once from all of these distribution lists,
92
all of these groups, all these entra groups.
93
I could have spent hours clicking through AD and clicking through entra,
94
but instead I just wrote a few scripts using ChatGPT in probably 10 to 15 minutes
95
and got it all done at once.
96
I also use scripts all the time for log filtering now.
97
Again, I used to go to event viewer and click and filter for the logs there.
98
Now you can just write a PowerShell script and it'll find you the exact logs, when they happened, what you need,
99
and you can move on with your life.
100
And that kind of efficiency gets you noticed.
101
You get stuff done.
102
And a bonus thing you've got to learn is understand basic networking.
103
You don't need to be a CCNA or CCNP networking beast, but if you can learn to trace
104
and troubleshoot a basic networking issue to gather information before you send it off to the network engineers, it's going to level you up.
105
So you definitely got to know ping.
106
You got to know trace route you got to use ipconfig
107
and you got to use these tools to actually reconcile against the documentation you have.
108
So if you run a trace route and the trace stops at some certain place, you need to find what is that IP?
109
Is that one of our devices?
110
Is that a different device?
111
Like where is this traffic stopping?
112
That information alone is crucial.
113
You got to understand what a default gateway is
114
and you got to understand what VLANs and subnets are and how these things work,
115
especially if you're working in a place that's going to have segmented networks, which you probably should be.
116
And then also just understanding when to hone in on the switch versus the endpoint versus the firewall.
117
Always start with the endpoint or the switch.
118
All right, so if you're serious about becoming a sysadmin, it starts with these three, four skills.
119
Read logs, understand infrastructure basics, DHCP, DNS, and then automate the boring stuff.
120
And learn a little bit of networking.
121
If you nail those things, you're not just on your way to sysadmin work, you're already doing it.
122
And if you wanna actually build these skills, start labbing, make a test tenant at home,
123
mess with DNS, and use your buddy ChatGPT to write some baby PowerShell scripts.
124
It doesn't matter if it's perfect what matters is that you're not waiting for permission from someone to start leveling up.
125
This is stuff you can do on your own.
126
And in IT in general, doing the work before someone actually gives it to you is the biggest factor for leveling up fast,
127
speed running the tiers, and going from zero to IT hero.
128
If this helps you guys, drop a like and a sub if that's your thing.
129
Really appreciate you guys.
130
Have a good day. Be safe. Be smart.
131
Make some good decisions.
132
Start leveling up.
앱 다운로드
유창하게 말하는 데 필요한 모든 것
AI 발음 평가문장마다 점수 확인
IPA 발음 연습모든 소리 마스터
단어 학습나만의 단어장 만들기
단어 게임놀면서 외우기
같은 채널
FOR YOU
추천 영상
C11
180 문장
Armchair Architects: Resiliency in the Cloud – Core Patterns
Daily ConversationUniversity StudentsWorking Adults
C1101 문장
BGP Overview
Daily ConversationUniversity StudentsWorking Adults
C13
173 문장
STOP Running Code On Your Computer
Daily ConversationUniversity StudentsWorking Adults
C12
272 문장
How I'd Learn n8n if I had to Start Over in 2026
Daily ConversationUniversity StudentsWorking Adults
C11
54 문장
Traceroute: You're Probably Reading the Results Wrong
Daily ConversationUniversity StudentsWorking Adults
C11
358 문장
It’s not just you
Daily ConversationUniversity StudentsWorking Adults
C11
433 문장
Give Me 24 minutes, I'll Give You 1,000+ hours of Claude Knowledge
Daily ConversationUniversity StudentsWorking Adults
B22
8 문장
Every Cybersecurity Beginner Should Watch This First (Networking Fundamentals)
Daily ConversationUniversity StudentsWorking Adults
C13
81 문장
Everything You Need to Know About DNS: Crash Course System Design #4
Daily ConversationUniversity StudentsWorking Adults
B21
336 문장
Best NextJS Folder Structures | Beginner - Intermediate - Advanced
Daily ConversationUniversity StudentsWorking Adults
C18
67 문장
8 Most Important System Design Concepts You Should Know
Daily ConversationUniversity StudentsWorking Adults
이 레슨의 어휘와 말하기 포인트
이 말하기 레슨은 영상 “Helpdesk to Sysadmin - 3 Things You Must Learn First”을(를) 바탕으로 합니다. 가장 자주 반복되는 단어는 다음과 같습니다: Dns, log, Dhcp, sysadmin, device. 이 영상에는 섀도잉할 문장 132개와 단어 1671개가 있습니다. 말하는 구간의 길이는 7:18입니다. 화자는 분당 약 229단어로 빠르게 말하므로 연음과 약하게 발음되는 소리가 많습니다. 영어에서 가장 많이 쓰이는 3,000단어에 속하는 단어가 80%뿐이라 어휘가 어려운 편입니다.
이 영상의 핵심 어휘
영상에 나오는 익혀 둘 만한 단어 15개를 발음, 뜻과 함께 정리했습니다.
| 단어 | 발음 | 뜻 |
|---|---|---|
| log 명사 | /lɔɡ/ | 통나무 |
| script 명사 | /skɹɪpt/ | 문서, 문장 |
| trace 명사 | /tɹeɪs/ | 흔적, 자국 |
| server 명사 | /ˈsɝvɚ/ | 서버, 봉사기 |
| resolve 동사 | /ɹɪˈzɑlv/ | 해결하다 |
| printer 명사 | /ˈpɹɪntɚ/ | 인쇄자 |
| desk 명사 | /dɛsk/ | 책상 |
| skill 명사 | /skɪl/ | 기술, 스킬 |
| versus | /ˈvɝsəs/ | 대 |
| filter 명사 | /ˈfɪltɚ/ | 여과기, 필터 |
| umbrella 명사 | /ʌmˈbɹɛl.ə/ | 우산 |
| vendor 명사 | /ˈvɛn.dɚ/ | 판매인, 판매자 |
| viewer 명사 | /ˈvju.ɚ/ | 관람자 |
| offline 형용사 | /ɔfˈlaɪn/ | 오프라인 |
| reboot 동사 | /ˈɹiːbuːt/ | 재시동한 위하여 |
따라 말해 볼 만한 문장
영상에 나오는 짧고 완결된 문장으로, 일상 대화에서 그대로 쓸 수 있습니다:
- You don't guess, you have to prove it.
- Is the name hosted inside your network or outside your network?
- Is that one of our devices?
주의할 발음
화자는 you're, don't, doesn't 같은 축약형과 약화된 형태를 39번 사용합니다. 들리는 대로 짧게 발음하세요.
- “sh”와 “zh” 소리: efficiency /ɪˈfɪʃ.ən.si/, substantial /səbˈstænʃəl/, crucial /ˈkɹuː.ʃəl/, documentation /ˌdɑkjəmɛnˈteɪʃən/, reservation /ˌɹɛz.ɚˈveɪ.ʃən/
- 긴 단어 — 강세 위치에 주의: infrastructure /ˈɪnfɹəˌstɹʌkt͡ʃə/, efficiency /ɪˈfɪʃ.ən.si/, investigate /ɪnˈvɛs.tə.ɡeɪt/, continuous /kənˈtɪn.juː.əs/, productivity /ˌpɹɒdʌkˈtɪvəti/
한국어 화자가 어려워하는 소리:
- /f/ — ㅍ(/p/)으로 바꾸지 말고 윗니를 아랫입술에 대기: filter /ˈfɪltɚ/, offline /ɔfˈlaɪn/, infrastructure /ˈɪnfɹəˌstɹʌkt͡ʃə/, efficiency /ɪˈfɪʃ.ən.si/, default /dɪˈfɔlt/
- /v/ — ㅂ(/b/)과 구별하기: server /ˈsɝvɚ/, resolve /ɹɪˈzɑlv/, versus /ˈvɝsəs/, vendor /ˈvɛn.dɚ/, viewer /ˈvju.ɚ/
- /z/ — ㅈ이 아니라 성대를 울리는 /s/: resolve /ɹɪˈzɑlv/, reservation /ˌɹɛz.ɚˈveɪ.ʃən/, analyze /ˈæn.əˌlaɪz/, oftentimes /ˈɔf.ənˌtaɪmz/
이 영상으로 연습하는 방법
- 먼저 말하지 않고 영상을 끝까지 듣고 모르는 단어를 적어 둡니다.
- 0.75배속으로 한 문장씩 섀도잉을 시작하고, 익숙해지면 보통 속도로 돌아갑니다.
- 자신의 목소리를 녹음해 원본과 비교하고, log, script, trace 같은 단어에 특히 주의합니다.
쉐도잉이란? 영어 실력을 빠르게 키우는 과학적 방법
쉐도잉(Shadowing)은 원래 전문 통역사 훈련을 위해 개발된 언어 학습 기법으로, 다언어 학자인 Dr. Alexander Arguelles에 의해 대중화된 방법입니다. 핵심 원리는 간단하지만 매우 강력합니다: 원어민의 영어를 들으면서 1~2초의 짧은 지연으로 즉시 소리 내어 따라 말하는 것——마치 '그림자(shadow)'처럼 화자를 따라가는 것입니다. 문법 공부나 수동적인 청취와 달리, 쉐도잉은 뇌와 입 근육이 동시에 실시간으로 영어를 처리하고 재현하도록 훈련합니다. 연구에 따르면 이 방법은 발음 정확도, 억양, 리듬, 연음, 청취력, 말하기 유창성을 크게 향상시킵니다. IELTS 스피킹 준비와 자연스러운 영어 소통을 원하는 분들에게 특히 효과적입니다.