ฝึกพูดภาษาอังกฤษด้วยเทคนิค Shadowing จากวิดีโอ: Are we heading to an era of stagnation or innovation?

กำลังสร้างบทเรียน...
1
Are we entering into an era of stagnation or endless innovation?
2
And this is a question I'm genuinely curious about.
3
And it's sort of asked at the end of my last video.
4
a little bit on like the effects of AI and
5
if people thought that it was going to cause stagnation
6
because the more we use AI to write code
7
and it's just based on the training data it already has
8
and then it's building more training data for it to look at
9
that it could potentially lead to an era of stagnation
10
and there's also the idea that there's less pressure for languages to actually evolve
11
if it the hard things don't matter that they're hard then why do the languages actually
12
sentiment that they were worried about that future where things just don't continue to go.
13
And there was a lot of people who were worried about the idea
14
that it just creates its own endless loop of building more and more training data based on the code that it's writing.
15
And another thing that came up was this idea of the average becoming the permanent ceiling.
16
And I actually thought that was really interesting that it came up
17
because I recently got back from CSS day where I had an
18
Stephen Hay was talking about that idea that where as long as we're using AI tools to do things,
19
it's always going to output average results because that's literally what they're basically made to do, right?
20
Or we're not made to do, but the way that they're just effectively like fancy autocompletes, they're just averaging things out all the time.
21
They're getting really good at that perhaps, but it still becomes what they're doing.
22
And so we just end up with average quality everything.
23
And in some cases, average is better than what's already being output.
24
So that's maybe around all of this as well, because sometimes it's not even average.
25
It's or the code it might be writing or the other things it's doing might be average, but there's doesn't really work within bigger system that's being built.
26
And then you run into problems and then it has trouble fixing those problems.
27
I'm not going to get into any of that.
28
But there was another side to this argument that came up
29
and it was this optimistic side on how LLMs and AI tools have the potential to actually
30
and have higher quality code being output, and higher quality other things, I guess as well, being put out.
31
And their main argument was that the training data isn't fixed, which is true, it's not.
32
It does rely on there being training data though, and that's a little bit of my worry.
33
People mentioned browser vendors, MDM documentation, and just the community at large, publishing high quality, up -to -date documentation.
34
We sort of have seen this a little bit with Google, so it's not to say it's not happening, right?
35
They put out the modern web guidelines, do a longer video on because I'm a little concerned with them.
36
I think there's like the the intention there is good.
37
I think that like most AI things, the promise that it sells is is a little bit overhyped.
38
And so anyway, I'm going to do something.
39
I need to.. see more with them and see if I'm right or wrong on that before I say anything.
40
I don't want to.
41
This is somewhere where I just talk about my opinion and my, you know, you can disagree with me.
42
That's completely fine.
43
But if I'm saying something doesn't work as intended, I do want to actually test it to to show or not as intended.
44
I think it's doing what it's intended to do, but the messaging around it is a little bit overselling it, which is what everything does these days.
45
Anyway, we're going off topic.
46
I want to talk about this idea of the training data in general.
47
And like one worry I have is for the MDM.
48
If you don't know the MDM, well, it's the Mozilla developer network.
49
It's not actually owned by Mozilla or run by Mozilla anymore.
50
It's not a company behind it.
51
It actually, almost all of it is written by two people.
52
There's Estelle who I did meet.
53
I've talked with her a few times and I met her at CSS Day.
54
She actually wrote the definitive guide to CSS along with Eric Meyer.
55
And so like she knows what she's doing and she writes tons of stuff for the MDM, one of I believe two people and she's not one of two people.
56
She's one of four people.
57
I just double checked.
58
So she's one of four people or four writers that work for the open web docs.
59
And this is a nonprofit organization who basically writes everything that's on the NBM.
60
And they don't have as much funding as you might think.
61
And there's you know, they get some funding from the browser vendors and stuff.
62
But like, they don't get enough.
63
And if they continue to not get enough, then maybe MDM starts being supported or an individual company starts doing it.
64
And that has its pluses and minuses that can come with it.
65
So let's just say like MDM stops happening because they don't or they're not getting enough funding now.
66
Everyone's like, oh, let's just use these AI tools instead.
67
So their funding goes down.
68
They end up, they have less writers, so it's not maintained enough or anything like that.
69
And there's less people that are fixing things in it because they're just finding the information there.
70
And we saw that with Tailwind, for example, where people aren't going to the docs as much as they used to
71
because they just let the AI write the stuff.
72
And then for the browser teams, like they're all massively understaffed as well.
73
You might think it's, oh, it's, you know, Apple and Google own these teams.
74
And yes, they own the browsers.
75
The teams that work for them are way smaller than you might expect and underfunded as well.
76
And they're making things right now like the web modern web guidelines.
77
But maybe, you know, and they don't have the funding for that anymore.
78
That can easily happen with a big company like Google that just doesn't see the benefit of having that type of thing.
79
And then what?
80
Then the training data does become stagnant.
81
And there's people like me, of course, making content and other people that are writing blog posts.
82
But all of those things are decreasing in views because people are not needing them as much.
83
And the less people are needing these things and we're more relying on the
84
potential for things to fall into some sort of you know, stagnation period instead.
85
And other people mentioned in the comments that it can also just look at the docs.
86
And I've always been like, yeah, it should just be looking at the docs from the beginning, but it's never actually done that.
87
They've never trained on the docs, but that's because they don't think.
88
They look they don't learn by reading the docs and then building stuff with it.
89
Maybe one day it can get good enough to be able to do that.
90
But they're not going to look at the CSS documentation
91
or the JavaScript documentation or the HTML documentation and then figure out how to do things.
92
doing that would probably be really high versus already the very high costs of training on existing code
93
that they just like look for patterns and figure things out that way.
94
That's more of what they're built to actually be able to do.
95
So yeah, I am personally a little bit worried about this less pressure for things to be innovating.
96
And why is this important, right?
97
Again, if hard.
98
Why is that a big deal?
99
But the web innovating is always a really important thing to do and not just the tools that are creating it.
100
But as more people are able to start making things for those things to be performant
101
and for them to be good for the user and everything else that comes with it.
102
And as our computers become more powerful and all these other things going on, if the languages behind them don't continue to innovate that's kind of boring right
103
and then we also all end up with like the same website
104
because they're all just eventually making
105
so much sameness i know we had like the bootstrap era
106
then the tailwind era now we have like the clode era where things are like oh
107
that was clearly a clode design i see it a lot on five coded websites
108
and that's a thing that happens and it's normal we go through these phases
109
but again if there's less innovation going on there's less people outside of the indie web i realize the indie that's amazing.
110
I'm so happy that the indie web is thriving.
111
There's so much fun stuff that goes on there.
112
And, you know, there we can push the limits and do crazy things, whether or not the language is innovating.
113
But yeah, the web itself, we're getting to a point now where we have so many things
114
that are becoming possible and more things on the horizon that are opening up all these amazing doors.
115
And it would just suck that if we don't see the potential of that, because the tools we're using are shortcuts where we don't actually need to continue to innovate anymore.
116
On top of who love this stuff are in it, right?
117
We're here, we're doing all of it.
118
If you're listening, maybe you are too, or maybe you're listening to it going, here's an old man who's shaking his fist at the clouds, doesn't like change.
119
But for those that are more in that camp, the thing i worry about there
120
and i know there's other ways to innovate you can create all these new things just through prompts
121
and that's amazing and it can feel like you're innovating
122
but again these these things aren't innovating they can allow people to work faster
123
which can lead to different types of innovation the other thing
124
i'm wondering about is just where you see the industry actually being in say five years from now
125
because i think the industry is still going to exist
126
and this is something that i'm thinking about right now i'm going to make another video on it but yeah
127
But I don't think it's going to be as drastically different as a lot of people think.
128
And I'm curious, do you think it's, you know, we've sort of are settling down now, people are starting to figure this out, and it's just we're making a lot more stuff because we can do things faster,
129
or is it all just going to fall apart, or something in between, or are all these new rules going to come up that we still haven't figured out yet?
130
Let me know in the comments below.
131
And with that, I'm going to say thank you very much for listening.
132
And of course, until next time, don't forget to make your corner of the internet just a little bit more awesome.

ทำไมต้องฝึกพูดกับวิดีโอนี้?

การฝึกพูดกับวิดีโอนี้ช่วยให้ผู้เรียนภาษาอังกฤษมีโอกาสที่จะเสริมสร้างทักษะการสื่อสารในสภาพแวดล้อมที่เปลี่ยนแปลงอย่างรวดเร็ว โดยเฉพาะเมื่อพูดถึงแนวคิดเชิงนวัตกรรมและความก้าวหน้าทางเทคโนโลยี เช่น AI ในการเขียนรหัส โดยผู้พูดตั้งคำถามเกี่ยวกับอนาคตของความก้าวหน้า ซึ่งทำให้เกิดการอภิปรายที่น่าสนใจเกี่ยวกับความเป็นไปได้ของการหยุดนิ่งหรือการสร้างนวัตกรรมใหม่ การได้ยินน้ำเสียงและการแสดงออกของผู้พูดจะช่วยให้ผู้เรียนเข้าใจบริบททางวัฒนธรรมและอารมณ์รวมถึงการใช้คำศัพท์ที่ชัดเจนและมีชีวิตชีวา

ไวยากรณ์และสำนวนในบริบท

  • การตั้งคำถาม: การตั้งคำถามเช่น "Are we entering into an era of stagnation or endless innovation?" ช่วยฝึกการใช้โครงสร้างประโยคคำถามในภาษาอังกฤษ ซึ่งสามารถนำไปใช้ในสถานการณ์จริงได้
  • การใช้คำเชื่อม: ประโยคเชื่อมเช่น "And this is a question I'm genuinely curious about." แสดงให้เห็นถึงการใช้คำเชื่อมเพื่อเชื่อมโยงความคิดอย่างมีประสิทธิภาพ
  • การใช้คำคุณศัพท์: ประโยค "it could potentially lead to an era of stagnation" ช่วยให้ผู้เรียนเห็นความสำคัญของการใช้คำคุณศัพท์ในเพื่อเพิ่มความหมายให้กับประโยค

กับดักการออกเสียงทั่วไป

ในการออกเสียงในวิดีโอนี้มีคำบางคำที่อาจจะทำให้ผู้เรียนพบกับอุปสรรค เช่นคำว่า "potentially" อาจจะยากในการออกเสียงให้ถูกต้องได้ นอกจากนี้ยังมีคำว่า "innovation" และ "average" ที่ผู้เรียนควรให้ความสนใจในการฝึกออกเสียงให้ได้อย่างถูกต้องและชัดเจน ซึ่งการปรับปรุงการออกเสียงภาษาอังกฤษเป็นสิ่งที่สำคัญ ผู้เรียนควรฝึกฝนบ่อยๆ เพื่อให้การออกเสียงของตัวเองคล่องแคล่วและเป็นธรรมชาติ

การทำความคุ้นเคยกับเสียงและจังหวะของผู้พูดในวิดีโอนี้จะช่วยให้ผู้เรียนเรียนรู้วิธีการพูดในแบบที่เหมาะสมและสอดคล้องกับการพูดจริงๆ นอกจากนี้ การใช้เทคนิค "shadowspeak" หรือการพูดตามเสียงของผู้พูดก็จะช่วยให้ผู้เรียนพัฒนาทักษะได้ดียิ่งขึ้น

ไวยากรณ์ในวิดีโอนี้

โครงสร้างที่ผู้พูดใช้บ่อยที่สุด พร้อมคำพูดจริงจากวิดีโอ:

โครงสร้างในวิดีโอ
Present perfect have/has + กริยาช่อง 3 — เหตุการณ์ในอดีตที่ยังเกี่ยวข้องกับปัจจุบันhave seen · I've talked · I've always been
Passive voice be + กริยาช่อง 3 — เน้นสิ่งที่เกิดขึ้น ไม่ใช่ผู้กระทำbeing built · being put · isn't fixed
Relative clauses who / which + อนุประโยค — ข้อมูลเพิ่มเติมเกี่ยวกับคนหรือสิ่งของpeople who were · fixed, which is

เทคนิค Shadowing คืออะไร?

Shadowing เป็นเทคนิคการเรียนรู้ภาษาที่ได้รับการรับรองทางวิทยาศาสตร์ พัฒนาขึ้นสำหรับการฝึกนักแปลมืออาชีพ วิธีการนี้เรียบง่ายแต่ทรงพลัง: คุณฟังเสียงภาษาอังกฤษจากเจ้าของภาษาและพูดตามทันที — เหมือนเงาที่ตามผู้พูดด้วยช่วงเวลาห่าง 1-2 วินาที การวิจัยแสดงว่าเทคนิคนี้ปรับปรุงความแม่นยำในการออกเสียง ทำนองเสียง จังหวะ การเชื่อมเสียง การฟังเข้าใจ และความคล่องแคล่วในการพูดได้อย่างมีนัยสำคัญ

เทคนิค shadowing: อ่านคู่มือฉบับเต็มทีละขั้นตอน →