跟读练习: Introducing Become an Epic Product Engineer - 通过视频学习英语口语
正在创建课程...
1
What is up everybody?
2
My name is Kent C.
3
Dodds, and this is Become an Epic Product Engineer podcast.
4
For the last 10 plus years, I've been teaching software developers how to build quality user experiences, primarily on the web.
5
And with the changing landscape of AI coding assistance, I am excited to introduce this new podcast series to help you learn the durable skills
6
that you can still use
7
and will continue to be able to use even as AI kind of takes over implementation from what we've typically been doing.
8
So yeah, software is changing.
9
AI is accelerating what was already true for even like 50 years ago.
10
One of the most valuable skills that you could have as a software developer is product engineering,
11
understanding users, their problems, and shipping what actually solves those user problems.
12
So yeah, sure, like quality, craft, review still matters, but agents are getting better at those things.
13
And so rapidly, the unique thing that we used to be able to provide,
14
which was coding, is sort of being eaten and taken over by AI.
15
And frankly, I love that.
16
I think it's awesome that we can spend more of our time really understanding the problem
17
and targeting what exactly our users actually need.
18
I like to think of it as the fact that, or the idea, the metaphor that we are all archers.
19
We've got this quiver of arrows and we've gotten really, really good at aiming at a target and letting go of the arrow,
20
letting it fly and hitting the target despite wind and other concerns.
21
But these arrows have been improving at a rapid pace with AI.
22
And so now they're less like arrows and more like homing beacons.
23
And yes, they don't always hit the target exactly right.
24
And you do have to be skilled at using these arrows.
25
But I am not very confident in my ability to predict
26
the future of what the ceiling is for these AI agents and how far or fast we're going to get there.
27
And so I think let's look at what the durable skill is.
28
And I think that is understanding what we are to build.
29
We've got so many targets that we could aim these arrows at.
30
And in fact, with as good as these arrows have gotten, we can hit other targets that we never even noticed before,
31
because now we just have these capabilities that we didn't really have before.
32
Lots of things have changed.
33
And so knowing what to build, that is what we're going to be talking about in this podcast series.
34
So the idea here is
35
that I want to learn out loud with the people who blend their technical depth and expertise with product judgment.
36
So these will be people that you have definitely heard about and people that you haven't heard about.
37
Founders, researchers, engineers, product managers who've kind of lived on both sides of things.
38
And we've already got, at the time I'm recording this, we've already got like a ton of episodes that I'm excited for you to dive into.
39
So yeah, I know like a lot of you engineers are worried about, oh man, like does AI mean that I'm just going to become a product manager now?
40
No, I actually don't think that that is the case.
41
Product managers are super valuable, but developers and their engineering experience and expertise is still super valuable.
42
And there is a distinction between what a product manager does and what a product engineer does.
43
But the fact is that a traditional software development
44
or software developer who's been doing this for a long time
45
does need to kind of adopt some of the mindset and the ideas that we typically associate with product manager.
46
Empathy for the user, developing clarity around a problem space so we can decide what solution to implement.
47
And then even identifying whether the problem is the right problem versus a beautifully wrong solution.
48
And I think that a lot of us can relate to that kind of thing.
49
So the through line here is that the mission here is I want to teach you durable skills.
50
I want to give you product thinking, not just code.
51
I want you to fall in love with the problem and not your solution.
52
as exciting as it is to develop really awesome solutions.
53
The real goal here is to get really good at understanding
54
that problem so that you can find a solution
55
that does a really good job solving that problem and maybe many other problems.
56
So we'll talk about like the problem tree and taking a step back and like, what is this problem actually?
57
So each episode, you're going to have a specific thing that you can do.
58
I call this the homework.
59
And the goal of that is just to get you actually doing stuff.
60
Now, you can definitely watch the episode and or listen to the episode
61
and learn a lot and just kind of have it,
62
you know, you can kind of marinate in that wisdom that these guests are sharing with us and from their experience.
63
But I think that actually taking action is where you're going to get a lot of value out of this.
64
And so at the end of every episode, I hope that you take the opportunity to jot down the homework and look for an opportunity to implement that,
65
whether that be read this book or talk to this person or whatever.
66
So I just want to kind of give you a sense for what you can expect here.
67
So a couple of specific episodes that already exist in the podcast series that I want to call out.
68
So Dax Rad actually was one of the people who inspired
69
me to start this podcast series in the first place
70
because he just comes out with these really great ideas of what it means to be a product engineer
71
and to build an actual product.
72
So he was the first episode and you definitely want to listen to that.
73
Now in that episode, he talks about how being faster at building the wrong thing is not good.
74
And actually intentionally adding restraint, which has now been removed because implementation is so fast,
75
intentionally adding that restraint will help you when like you're just actively putting features in front of users' faces and stuff.
76
We talk about the onboarding experience and how to avoid the kitchen sink clutter of like a command K sort of experience.
77
He's building a dev tool.
78
So that one is a really great episode.
79
Wayne Allen, also a really awesome episode.
80
He has some classical training where he's really studied up on what product engineering actually is.
81
And so we talk about building the right thing before we build the thing right, validate before we fall in love with the idea, that sort of thing.
82
We've talked about the mom test.
83
It's really good.
84
You want to listen to that one for sure.
85
And Will's episode is also fantastic.
86
He's got some actual formal training in this area with instructional or with industrial design.
87
And there are a lot of really interesting crossovers with that.
88
So don't miss that episode.
89
Don Norman, the author of The Design of Everyday Things, along with many other books, he's 90 years old.
90
And he comes on the podcast to talk about his experience over the history.
91
And he talks about what that user error actually just means that the design and the system has a problem.
92
and why you really want to watch real people using your software.
93
And Grady Booch, actually, at the time I'm recording this episode or this intro for you, Grady Booch's episode has not actually been published.
94
So you can look forward to that episode.
95
He talks a lot about judgment, architecture, what doesn't get automated, what should get automated, that sort of thing.
96
He actually, that episode happened because I posted something to EpicProduct.Engineer titled The Last Software Engineer,
97
which is just a metaphor that I use to talk about product engineering and why it's so important.
98
But he took issue with that title and some of the things that I shared in that post.
99
And so we have a really nice conversation about the way that he sees the future.
100
It's really interesting.
101
Alex Hillman, Sales Safari, he's got a really great mind for
102
understanding how to engineer desire before you build out a spec
103
and how to help people feel anticipated rather than tricked as they're using your software really really good dylan also fantastic episode.
104
He talks about making user pain feel painful for you, integrating directly with support and tightening that user feedback loop.
105
Really great episode.
106
And Aaron Francis, that episode was really great because he's building Solo,
107
a software called Solo and talks about his experience as an indie developer building that for development users.
108
So we've got that and way, way more.
109
So many awesome episodes that I'm excited for you to experience as you go through this podcast series.
110
So you don't necessarily need to go things in order.
111
The episodes are not linear in any way.
112
So just grab whatever episodes you want to.
113
If you want to binge the whole thing, that's probably how I would consume this because every one of these episodes is just fantastic.
114
I'm not going to publish an episode that isn't fantastic.
115
I also ask you to please subscribe.
116
And you can actually go to the website, epicproduct.engineer slash become an Epic Product Engineer podcast,
117
all with hyphens, or you just look for it on the internet.
118
And you can actually submit your email and your name.
119
And I will send you an email every week with a summary of an episode.
120
And so if you just want that, like constantly in the back of your mind that you're trying to become an Epic Product Engineer,
121
then that is a really great way to do that.
122
And also on the site, there are episode summaries and the homework is there.
123
There's show notes and transcripts and all of that too.
124
But yeah, every week you can look forward to getting a new episode on Wednesday.
125
One last thing that I wanna mention too is I'm actually also starting a new series
126
that is like a solo companion to this where I am creating a series titled Better with Kent,
127
where we're all going to get better with Kent.
128
And we're going to talk about durable skills that you can develop on that.
129
So go search up Better with Kent on your favorite podcast player.
130
This will also be a YouTube series.
131
And we're going to talk about how you can make yourself a better,
132
more useful and value creating individual as a software developer.
133
So with that, I'm going to leave you with your homework.
134
This is the homework.
135
Your homework is to subscribe to the podcast in whatever your favorite podcast player or whatever, and pick one episode, just one that you're going to listen to.
136
And if that episode wins you over, then I invite you to come back again and continue to listen to the rest of the episodes.
137
So thank you so much for listening to this episode.
138
And I'm looking forward to seeing you throughout all of the episodes of the Become an Epic Product Engineer podcast.
139
Thank you so much.
140
We'll see you around.
为什么通过这个视频练习口语？
通过观看和模仿Kent C. Dodds在《成为一名出色的产品工程师》播客中的讲话，您可以有效地提高英语发音和流利度。这个视频提供了关于如何理解用户问题和工程思维的深刻见解，适合那些希望在软件开发领域提升表达能力的学习者。通过反复练习，您将掌握与产品工程相关的术语和表达方式，这对雅思口语练习也是非常有帮助的。
语法与表达在上下文中的使用
在视频中，Kent使用了几种关键的语言结构，这些结构对于提高英语发音和理解产品工程的讨论至关重要：
- 理解用户的问题: "理解用户的需求是我们解决问题的关键。"这里的句子结构强调了主语和宾语之间的关系，有助于学习者理解如何表达复杂的概念。
- 如何定义解决方案: "识别正确的问题比实施错误的解决方案更重要。"这是一种体现逻辑思维的表达，学习者可以模仿这种句型，增强逻辑表达能力。
- 产品思维: "我想教你们有耐久性的技能。"使用“想教”和“有耐久性的技能”这样的搭配，可以帮助学习者更好地理解目标导向的讨论方式。
常见发音陷阱
在视频中，有几个单词和短语的发音可能会对学习者构成挑战：
- engineering（工程）: 注意音节的重音，确保在发音时强调第二个音节。
- product management（产品管理）: 常常会有连读现象，学习者需要练习流畅地将两个词连接。
- AI: 作为一个常用的术语，它的发音涉及较为简洁的音节，需要确保“艾”的发音清晰连贯。
通过这些练习，您将能够提高您的英语发音，并在应用中感受到这些表达方式的魅力。适当地利用这些技巧，结合雅思口语练习和shadow speak的方法，定能产生更好的学习效果。
什么是跟读法？
跟读法 (Shadowing) 是一种有科学依据的语言学习技巧，最初开发用于专业口译员的培训，并由多语言者Alexander Arguelles博士普及。这个方法简单而强大：您在听英语母语原声的同时立即大声重复——就像是一个延迟1-2秒紧跟说话者的影子。与被动听力或语法练习不同，跟读法强迫您的大脑和口腔肌肉同时处理并模仿真实的讲话模式。研究表明它能显着提高发音准确性，语调，节奏，连读，听力理解和口语流利度——使其成为雅思口语备考和真实英语交流最有效的方法之一。