Luyện nói tiếng Anh bằng Shadowing qua video: NVIDIA CEO on Elon Musk, xAI, Colossus supercomputer and systems engineering | Jensen Huang

you've highly lauded Elon and XAI's accomplishment in Memphis in building Colossus supercomputer,

⏸ Tạm dừng

Tốc độ:

97 câu

Nếu các câu quá ngắn hoặc quá dài, hãy bấm Edit để chỉnh sửa.

you've highly lauded Elon and XAI's accomplishment in Memphis in building Colossus supercomputer,

probably in record time in just four months.

It's now at 200,000 GPUs and growing very quickly.

Is there something that you could speak to,

understand about his approach that's instructive broadly to all the data center creators that enable that kind of accomplishment?

his approach to engineering, his approach to the whole management of construction, everything.

First of all, Elon is deep in so many different topics,

yet he's also a really good systems thinker.

And so he's able to think through multiple disciplines.

And he obviously pushes things,

questions everything, whether number one, is it necessary?

number two does it have to be done this way

and in other words you know does it have does it have to take this long

and and so

so he he has he has the he has the ability

uh to question everything uh to the point where everything is

down to its minimal amount that's necessary you can't take anything else out

and and yet yet the the the the the necessary um capabilities of the product retains you know

and so he's he is as minimalist as you could possibly imagine

and he does it at a system system scale um i i also love the fact

that he he is um he is represented he he is he is present at the point of action.

You know, he'll just go there.

If there's a problem, he'll just go there and show me the problem.

You know, when you do all of this in combination,

you overcome a lot of previous,

this is just the way we do it.

You know, I'm waiting for them.

You know, I mean, it's just,

everybody has a lot of excuses.

And so, and then the last thing is,

When you act personally with so much urgency,

it causes everybody else to act with urgency.

Every supplier has a lot of customers going on.

Every supplier has a lot of projects going on.

He makes it his business that he's the top priority of everybody else's projects.

He does that by demonstrating it.

I've been in a bunch of those meetings.

It's fun to watch because really not enough people ask the question like,

okay, so can this be done a lot faster and how?

Why does it have to take this long?

Yeah, right.

And then that becomes an engineering question often.

And yes, I think when you get the ground truth of actually,

I remember one of the times I was hanging out with him,

he literally is going through the entire process of how to plug in cables into a rack.

He's working with an engineer on the ground that's doing that task,

and he's just trying to understand what does that process look like so it can be less error-prone.

And just building up that intuition from every single task involved in putting together the data center,

you start to immediately get a sense at the detailed scale and at the broad system scale of where the inefficiencies are.

And so you can make it more and more and more efficient.

Plus, you have the big hammer of being able to say,

let's do it totally different and remove all possible blockers.

That's right.

is there parallels in the nvidia extreme systems code design approach that you see in the way Elon approaches systems engineering?

Well, first of all, co-design is an ultimate systems engineering problem.

And so we approach the work that we do from that principle.

The other thing that we do,

and this is a philosophy that,

a thought, a state of mind,

I guess, a method that I started 30 years ago,

and it's called the speed of light.

A speed of light is not just about the speed.

A speed of light is my shorthand for what's the limit of what physics can do.

And so everything that we do is compared against the speed of light.

Memory speed, math speed, power,

cost, time, effort, number of people, manufacturing cycle time.

and when you think about latency versus throughput,

when you think about cost versus throughput,

cost versus capacity, all of these things,

you test against the speed of light to achieve all of these different constraints separately.

And then when you consider it together,

you know you have to make compromises because a system that achieves extremely low latency

versus a system that achieves very high throughput are architected fundamentally differently.

But you want to know what's the speed of light of a system that achieves high throughput?

What's the speed of light of a system that achieves low latency?

And then when you think about the total system, you could make trade-offs.

And so I force everybody to think about what's the first principles,

the limits the physical limits um for everything before we you know before we uh do anything

and and we test everything against that and

so that's a good frame of mind i don't love the other methods which is continuous improvement

the problem with continuous improvement it first of all you should

engineer something from first principles at the speed you know with speed of light thinking limited only by physical limits

and and physics limits and um after

that of course you would improve it over time um

but i don't like going into a problem

and somebody says hey you know it takes 74 days to do this today right now

and we can do it for you in 72 days you know i'd rather strip it all back to zero

and say first of all explain to me why it's 74 days in the first place

and let's think about what's possible today.

And if I were to build it completely from scratch,

how long would it take?

Oftentimes you'd be surprised and might come to six days.

Now the rest of the six days to 74

could be very well-reasoned and compromises and cost reductions and all kinds of different things,

but at least you know what they are.

And then now that you know that six days is possible,

Then the conversation from 74 to 6 Surprisingly much more effective

TRENDING

Phổ biến

Phương Pháp Shadowing Là Gì?

Shadowing là kỹ thuật học ngôn ngữ có cơ sở khoa học, ban đầu được phát triển cho chương trình đào tạo phiên dịch viên chuyên nghiệp và được phổ biến rộng rãi bởi nhà đa ngôn ngữ học Dr. Alexander Arguelles. Nguyên lý cốt lõi đơn giản nhưng cực kỳ hiệu quả: bạn nghe tiếng Anh của người bản xứ và lặp lại to ngay lập tức — như một "cái bóng" (shadow) đuổi theo người nói với độ trễ chỉ 1–2 giây. Khác với luyện ngữ pháp hay học từ vựng bị động, Shadowing buộc não bộ và cơ miệng phải đồng thời xử lý và tái tạo ngôn ngữ thực tế. Các nghiên cứu khoa học xác nhận phương pháp này cải thiện đáng kể phát âm, ngữ điệu, nhịp điệu, nối âm, kỹ năng nghe và độ lưu loát khi nói — đặc biệt hiệu quả cho người luyện IELTS Speaking và muốn giao tiếp tiếng Anh tự nhiên như người bản ngữ.

ShadowingEnglish.com – Luyện Nói Tiếng Anh Bằng Shadowing

Nói tiếng Anh lưu loát với phương pháp Shadowing — nghe người bản xứ, đọc theo từng câu, rèn phản xạ ngôn ngữ thật sự. Được hàng ngàn người học IELTS tin dùng.

Luyện nói tiếng Anh bằng Shadowing qua video: NVIDIA CEO on Elon Musk, xAI, Colossus supercomputer and systems engineering | Jensen Huang

Phổ biến

Bối Cảnh & Nền Tảng

Top 5 Câu Nói Dùng Trong Giao Tiếp Hằng Ngày

Hướng Dẫn Shadowing Bằng Bước

Phương Pháp Shadowing Là Gì?

Luyện nói tiếng Anh bằng Shadowing qua video: NVIDIA CEO on Elon Musk, xAI, Colossus supercomputer and systems engineering | Jensen Huang

Tải Ứng Dụng

Bối Cảnh & Nền Tảng

Top 5 Câu Nói Dùng Trong Giao Tiếp Hằng Ngày

Hướng Dẫn Shadowing Bằng Bước

Phương Pháp Shadowing Là Gì?