シャドーイング練習: A Career in IT - 動画で英語スピーキングを学ぶ
読み込み中...
1
Welcome to The Explainer, everyone.
2
Today, we're diving into something really fascinating.
3
We're unpacking a source document that maps out a two-decade career in IT infrastructure.
4
But look, we're not just reading off a resume here.
5
We're basically looking at a masterclass in problem solving.
6
We're going to see exactly how an engineer's mindset evolves right alongside the crazy tech they're building.
7
Let's kick things off with this massive number, 20.
8
For nearly 20 years, this person has been in the trenches of IT.
9
We're talking infrastructure, cloud, DevOps, SRE, production operations, the whole shebang.
10
Just think about how much the tech world has changed in that time.
11
I mean, we've gone from literally racking bare metal servers in a phrasing called data center to orchestrating these wildly complex multi-cloud ecosystems.
12
It's a huge paradigm shift.
13
So let's dive into this timeline and map out the four major eras we'll be exploring today.
14
We start way back in 2006 at a place called FIBO.
15
Then we jumped to VNG in 2012, hit a massive turning point at SmartPay in 2020, and finally land right in the present day with Masson Group.
16
And trust me, every single stop on this journey brings a totally different scale of tech.
17
Section 1.
18
The Foundation.
19
Linux and Bare Metal.
20
Okay, picture it.
21
The year is 2006 at a hosting company called Feebo.
22
Starting a career here wasn't just, you know, occasionally checking a server to see if a green light was blinking.
23
The workload covered absolutely everything.
24
We're talking Linux servers, the really early days of virtualization, networking, and even direct customer support.
25
It was basically a foundational boot camp where you had your hands in every single piece of the puzzle, including probably lugging some incredibly heavy physical servers around.
26
Now, there's a quote from this era that brilliantly captures the core philosophy forged in those early days.
27
It goes like this.
28
When there's a production problem, you need to stay calm, understand what's really happening, and find a practical solution.
29
That mindset right there, that is absolutely crucial.
30
It becomes the ultimate anchor.
31
Because as you'll see, when you're in a production problem, you need to stay calm, understand what's really happening, and find a practical solution.
32
That mindset right there, that is absolutely crucial.
33
It becomes the ultimate anchor.
34
Because as you'll see, when you're dealing with massive global deployments later on, panic simply isn't an option.
35
You really have to lean on that foundational discipline.
36
Section 2.
37
Scaling up.
38
The jump to millions.
39
Jumping ahead to 2012, the move to VNG brought a literal exponential leap in complexity.
40
suddenly you're not just supporting a few clients the environment shifted
41
to platforms supporting millions of active users the day-to-day focus totally
42
changed to advanced system monitoring building out content delivery networks and eventually managing an open stack private cloud
43
running systems for millions of users that teaches you some intense high-stakes lessons in scalability automation, and hardcore system reliability.
44
And of course, right alongside that massive technical growth came real professional growth.
45
The subject stepped up into the role of lead system engineer.
46
This wasn't just a fancy new title on a business card either.
47
It meant taking on serious ownership and stepping up to lead and mentor other engineers in a really high-pressure environment.
48
Section 3.
49
The App Ops Transformation.
50
Redesigning SmartPay.
51
Now we jump to 2020 and enter SmartPay.
52
This was arguably the most critical stage of the whole journey
53
because the mindset shifted from just scaling systems to actively enabling the entire business.
54
This massive technical turnaround happened in three really clear steps.
55
Step one, redesigning and stabilizing the databases.
56
They had to get deep into the weeds of production issues, fixing slow queries, clearing up database deadlocks, getting real monitoring on IOPS.
57
Then step two, a massive migration over to Kubernetes.
58
And finally, step three, building out total top to bottom system observability.
59
Actually, let's just pause on that second step for a second because the sheer scale of it is wild.
60
They didn't just tanker with Kubernetes.
61
They built the entire platform and orchestrated the migration of hundreds of microservices.
62
Hundreds, all moving from traditional virtual machines straight into Kubernetes.
63
And they were doing this while juggling major cloud platforms like AWS, GCP, and Azure all at once.
64
So how do you manage all that crazy new complexity? you build centralized observability solutions entirely from scratch.
65
We're talking unified logging, metrics, tracing, alerting, the whole nine yards.
66
And why does this actually matter?
67
Well, having all of this data in one central place made it
68
so much easier for the engineering teams to see what was actually breaking in production and troubleshoot incidents fast.
69
It completely took the guesswork out of the equation.
70
So the crucial point here is that this whole SmartPay experience forced a total mindset shift.
71
The old legacy view was that infrastructure is just about servers, networks, or Kubernetes clusters.
72
But the new view, the realization they came to after building this AppOps team from scratch to boost payment reliability,
73
it's that infrastructure is entirely about enabling the business and engineering teams.
74
Tech is just the tool.
75
The real goal is business reliability.
76
Section 4.
77
Leading Modern Cloud Strategy.
78
Mastering Multi-Cloud at Masan Group.
79
Moving over to Mazan Group as the senior manager of cloud and infrastructure, the role zoomed out to a much more strategic level.
80
They took on leadership of a team of around 10 engineers.
81
And this team had a huge surface area to cover, everything from DevOps and centralized CICD to SRE.
82
So while the role naturally became much more strategic, guiding cloud transformation and modernizing infrastructure, it crucially remained deeply hands-on.
83
And I want to show you exactly what hands-on means when we talk about modern infrastructure.
84
They were managing a sprawling, highly complex, multi-cloud environment, starting with Microsoft Azure,
85
then quickly expanding into Amazon Web Services as a core part of that ecosystem.
86
Layering in Google Cloud Platform to handle specific, specialized workloads.
87
And finally, topping it all off with Oracle Cloud Infrastructure, not to mention a fleet of traditional on-premises servers.
88
Trying to manage workloads across all of these disparate platforms simultaneously, it's literally an orchestration masterpiece.
89
requires just an incredibly deep understanding of how all these different systems securely talk to each other.
90
Section 5, the problem solver's future, an engineer at heart.
91
But here's the thing, despite the senior management titles, and despite the sheer scale of the architectures being designed today,
92
this person is and always will be an engineer at heart.
93
And really, what you should take away from this explainer is the ultimate driver behind a career like this.
94
It's not just about climbing the corporate ladder.
95
It's that visceral thrill of finding the root cause when the pager goes off at 3 a.m.
96
It's the joy of designing a really elegant platform.
97
It's automating away the boring stuff and teaming up with other engineers to build something amazing.
98
In fact, I absolutely love this quote from the source document because it perfectly sums up everything we've been talking about.
99
They say, I don't just want to manage people.
100
I want to continue building, learning, solving difficult problems, and helping engineering teams create reliable and scalable systems.
101
They are actively looking for an international environment where they can combine their hardcore tech skills, their obsession with problem solving and their leadership experience into one role.
102
And that leaves us with a really fascinating question to think about.
103
When you reach the absolute highest levels of IT infrastructure,
104
how do you balance strategic leadership with that burning fundamental need to actually build things with your own two hands?
105
It's basically the ultimate challenge for the modern technical leader.
106
Thanks so much for joining me on on this explainer today and hey, keep solving those complex problems.
このレッスンについて
「A Career in IT」を使って、シャドーイングで英語を練習しましょう。
毎日15〜30分の練習で、IELTSスピーキングへの自信と実践的な英会話力が身につきます。
シャドーイングとは？英語上達に効果的な理由
シャドーイング（Shadowing）は、もともとプロの通訳者養成プログラムで開発された言語学習法で、多言語習得者として知られるDr. Alexander Arguelles によって広く普及されました。方法はシンプルですが非常に効果的：ネイティブスピーカーの英語を聞きながら、1〜2秒の遅延で声に出してすぐに繰り返す——まるで「影（shadow）」のように話者を追いかけます。文法ドリルや受動的なリスニングと異なり、シャドーイングは脳と口の筋肉が同時にリアルタイムで英語を処理・再現することを強制します。研究により、発音精度、抑揚、リズム、連音、リスニング力、そして会話の流暢さが大幅に向上することが確認されています。IELTSスピーキング対策や自然な英語コミュニケーションを目指す方に特におすすめです。