ฝึกพูดภาษาอังกฤษด้วยเทคนิค Shadowing จากวิดีโอ: Spec-Driven Development: AI Assisted Coding Explained

Right now, the way apps are getting built is completely changing because before writing and reviewing code was the hardest part,

but now it's knowing how to effectively convey what you want to build with an LLM.

And that, my friends, is what's known as spec-driven development.

Thank you very much.

Nah, I'm just kidding because the thing is spectrum

and development has become one of the most important skills to learn

if you're looking to be an AI engineer Or to use AI to help build your applications,

but let me explain why it's different from a common technique that you might also know Which is a vibe coding, right?

And this is typically what people think of when they think of AI assisted coding or coding agents

So I want to give you a quick example of what vibe coding typically looks like

And we'll kind of compare how this is different than spec coding here in a second But as a user, as a developer,

as a builder What you're going to start from is typically your AI coding agent Whether it's in a browser

or it's on your machine itself You're going to start from

that initial prompt So you're going to write that initial prompt to the LLM and say hey,

I want a specific application that does this functionality in this specific language like Java or Python.

And that prompt is then sent to the model.

And that model is then going to start generating code based on what it thinks

that you want from that project and that it's been trained on as well.

So at this point, we've got some boilerplate code.

And this is great for testing.

That's why I love Vibe Coding 4.

And we're going to go from here.

But the thing is, we might not have the exact desired implementation that we want.

So we're going to go ahead and edit that prompt.

So we're going to say, actually, I wanted something different or to use a different type of library or something like that.

So we'll go from the prompt editing over to the AI still continuing to code.

And we'll go back and forth until we reach that desired implementation after a few tries, right?

So we are at the desired state of implementation.

So that's typically what we see when we're doing vibe coding.

But the thing is like, how did, for example,

the AI model decide to make that specific decision that it did based on the prompt that we gave?

Because we could do a hundred different tries of this implementation of the app we want to create.

We might get a different result every time, and that frustrates a lot of people.

And the thing is, Vibe Coding kind of skips the traditional software delivery lifecycle also known as the SDLC

that we're used to in software engineering.

The software development lifecycle takes a little bit of a different approach

because we start our project by planning and designing using specific project requirements

or the PRD as it's typically called and then we take what we need

and require for our project and begin to implement those features.

Once we have those features we test to see if if they work.

We do a little bit of quality assurance

and then it goes into the deployment phase from dev to staging to production and finally the maintenance of that project.

And so while vibe coding is fantastic and I know it feels like magic, spec coding takes a little bit of a different approach

and adds in some of these software development lifecycle components to AI generated software development.

So let's take a look at what spec coding looks like in a hypothetical scenarios.

So spec coding or spec driven development, again, is going to take into consideration some of those software development lifecycle aspects, right?

But also use the LLM just like Vibe coding in order to, as an AI agent, write code or run these tests.

But it all starts with the prompt, of course, at first.

But the thing is, we're not prompting a specific implementation.

We're prompting what we want our system to do.

So the behavior, the constraints that we want and

that specific specification is then used like a contract to create a requirements

and this requirements is going to be kind of the main hierarchy of how this project is going to work

so how we want the model

and the agent to write code to do tests documentation verification

and much much more is all going to be focused from around the requirements itself the thing is

If we're happy with those requirements, so if we're happy, we can approve, and we can say, yes,

I want to turn this requirement specification into a design document that will then have to-dos for each specific implementation.

Or I can say, hey, I want to edit how I want this project to be implemented.

Because at this point, nothing has been implemented, and AI models are all about proper instructions.

So having a spec like this is much better than having

the LNM guess what solution is going to hopefully best fit the user's request.

So we go from the design here and if we're happy with

that design and how we actually want it to be implemented in code, well then we can have the model if we're happy go off and implement this.

So we can go and use that AI agent

or we can continue to do more requests on the specific implementation features

that we want to get back to and that's how spec coding works.

But Really quickly, I want to explain how it's different than other development cycles.

So in traditional development, so the way that, you know, most folks kind of started by writing code, it was first code, right?

And then afterwards, it was documentation, right?

So we would kind of start with our intuition and we would kind of go from there.

The thing is, we also started to work with test-driven development.

So test-driven development, as you can probably assume in the name, is where we start from the test and what the functionality we want for this,

you know, applications behavior to be, and then go into writing the code afterwards.

So that was also another popular way to approach development.

And the thing with spec coding, so spec-driven development, is it kind of turns it on its head.

So we kind of go from specifications these specs

that we have here to the design document requirements and actually implementing

that And then we go to code and so it's kind of test driven development and behavior Driven development on steroids, which is really cool

So let me give you a quick example of how this works in practice So we'll start off with vibe coding.

So with vibe coding again, we're just talking to the model We're doing quick edits on the fly.

I think that's that's what it's best for, right?

We're gonna say, hey, we need, let's see, what do we need?

Maybe a slash login page for our users to authenticate.

So, okay, that's a great request to the model, but how do we know what it's gonna do?

It might have 30 different ways to implement this, and we might have to go back and forth with the model, and that can take sometimes longer than just writing the code ourselves.

So vibe coding is one way to approach that problem.

The spec-driven development approach is a little bit different,

but of course still using the LLM to create this requirement that we have for this feature, right?

So in this case with spec-driven development, we're going to have a new feature and this feature is going to be user authentication, right?

So this is a new feature that we want to the LLM to build out.

Of course, we haven't started implementing yet.

This is just the kind of planning phase.

And we're going to say, hey, this is going to be an endpoint at slash login to do post requests to.

Okay, awesome.

And then what variables are we going to take for the username and password?

Well, we can say, hey, we're going to accept two different variables.

So they're going to be user and then pass.

Awesome.

100

So that is in there.

101

And we know when the implementation starts why it got to this conclusion.

102

Let's say for some reason if it doesn't work, we're going to have a fallback, a failure code.

103

If missing, I don't know, let's say username, right?

104

And then we can also generate test cases from here.

105

So let's go on to test and we're going to say,

106

hey, valid credentials will give a 200 code.

107

And this is really cool because when we're doing AI-assisted coding, we now have less ambiguity for our coding agents,

108

and we can use spec-driven coding to kind of flip the traditional development model, right?

109

So that we have this spec, and that becomes the primary artifact that drives all this downstream work like implementation and test and much more.

110

If you learned something today, I'd love if you could hit the like button and hack the algorithm, and make sure you subscribe for more content around AI and application development.

111

Have a good one.

📺 ช่องเดียวกัน

✨ วิดีโอแนะนำ

117 ประโยค

I've Changed My Opinion On DEVELOPERS Vibe Coding

Business EnglishUniversity StudentsWorking Adults

674 ประโยค

FULL Data Science Mock Interview | SQL, Statistics, Business

Business EnglishInterview EnglishUniversity Students

94 ประโยค

Your AI broke the layout. Now what?

Business EnglishUniversity StudentsWorking Adults

214 ประโยค

New Skills! v1.3 brings /pr, /implement-spec, and /retro

Business EnglishUniversity StudentsWorking Adults

20 ประโยค

Is prompt engineering dead? Advice on optimizing AI interactions | Amazon Web Services

Business EnglishUniversity StudentsWorking Adults

96 ประโยค

Design Patterns in Java Theory

Business EnglishUniversity StudentsWorking Adults

12 ประโยค

Rapid Engineering With AI

Business EnglishUniversity StudentsWorking Adults

126 ประโยค

How I use AI as a senior software engineer and 5 principles of AI explained in 10 minutes

Business EnglishUniversity StudentsWorking Adults

309 ประโยค

Claude Code: The Advanced Guide (99% of Devs Skip These Features)

Business EnglishUniversity StudentsWorking Adults

14 ประโยค

CS50x 2026 - Introduction

Business EnglishUniversity StudentsWorking Adults

185 ประโยค

15 Minutes to Fix Your AI Dev Workflow with OpenCode

Business EnglishUniversity StudentsWorking Adults

คำศัพท์และข้อสังเกตด้านการพูดสำหรับบทเรียนนี้

วิดีโอนี้มี 111 ประโยค และ 1586 คำ สำหรับฝึกพูดตาม ช่วงที่มีเสียงพูดยาว 8:56 ผู้พูดพูดด้วยความเร็วเป็นธรรมชาติ ประมาณ 177 คำต่อนาที ใกล้เคียงกับบทสนทนาในชีวิตประจำวัน 85% ของคำอยู่ใน 3,000 คำที่ใช้บ่อยที่สุดในภาษาอังกฤษ ส่วนที่เหลือควรดูไว้ก่อนเริ่มฝึก

คำศัพท์สำคัญในวิดีโอนี้

คำที่ควรเรียนรู้ 15 คำจากวิดีโอ พร้อมคำอ่านและความหมาย:

คำศัพท์	คำอ่าน	ความหมาย
edit คำกริยา	/ˈɛdɪt/	แก้ไข
username คำนาม		ชื่อผู้ใช้
technique คำนาม	/tɛkˈniːk/	เทคนิค, กลเม็ด
compare คำกริยา	/kəmˈpɛɚ/	เปรียบเทียบ
spectrum คำนาม	/ˈspɛktɹəm/	สเปกตรัม
scenario คำนาม	/sɪˈnɛəɹioʊ/	ฉากทัศน์
approve คำกริยา	/əˈpɹuːv/	อนุมัติ
password คำนาม	/ˈpæs.wɜɹd/	รหัสผ่าน, รหัส
algorithm คำนาม	/ˈælɡəɹɪðm̩/	ขั้นตอนวิธี, อัลกอริทึม
builder คำนาม	/ˈbɪl.dəɹ/	ผู้สร้าง, ผู้ก่อสร้าง
convey คำกริยา	/kənˈveɪ/	ถ่ายทอด, ลำเลียง
hierarchy คำนาม	/ˈhaɪ.ə.ɹɑː(ɹ).ki/	ลำดับชั้น
intuition คำนาม	/ˌɪn.tjuːˈɪʃ.ən/	อัชฌัตติกญาณ
ambiguity คำนาม	/æm.bɪˈɡjuː.ɪ.ti/	ความกำกวม
spectacles คำนาม	/ˈspɛktəkl̩z/	แว่นตา

กริยาวลีที่คุณจะได้ยิน

คำศัพท์	ความหมาย
go back คำกริยา	กลับไป

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

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

โครงสร้าง	ในวิดีโอ
Passive voice be + กริยาช่อง 3 — เน้นสิ่งที่เกิดขึ้น ไม่ใช่ผู้กระทำ	been trained · be focused · be implemented
Present perfect have/has + กริยาช่อง 3 — เหตุการณ์ในอดีตที่ยังเกี่ยวข้องกับปัจจุบัน	has become · has been implemented · haven't started
Relative clauses who / which + อนุประโยค — ข้อมูลเพิ่มเติมเกี่ยวกับคนหรือสิ่งของ	know Which is · steroids, which is

การออกเสียงที่ควรระวัง

ผู้พูดใช้รูปย่อและรูปลดเสียง 37 ครั้ง เช่น we're, we'll, you're ให้พูดแบบสั้นตามที่ได้ยิน

เสียง “th”: algorithm /ˈælɡəɹɪðm̩/, hypothetical /ˌhaɪpəˈθɛtɪkəl/, authenticate /ɔˈθɛn.tɪ.keɪt/, authentication /ɔːˌθɛntɪˈkeɪʃn̩/
เสียง “sh” และ “zh”: speculation /ˌspɛk.jəˈleɪ.ʃən/, implementation /ˌɪmplɪmənˈteɪʃən/, documentation /ˌdɑkjəmɛnˈteɪʃən/, conclusion /kənˈkluːʒən/, consideration /kənˌsɪd.əˈɹeɪ.ʃən/
คำยาว — ลงเสียงหนักให้ถูกพยางค์: speculation /ˌspɛk.jəˈleɪ.ʃən/, implementation /ˌɪmplɪmənˈteɪʃən/, documentation /ˌdɑkjəmɛnˈteɪʃən/, consideration /kənˌsɪd.əˈɹeɪ.ʃən/, developer /dɪˈvɛləpɚ/

วิธีฝึกกับวิดีโอนี้

ฟังวิดีโอให้จบหนึ่งรอบโดยยังไม่ต้องพูด แล้วจดคำที่ยังไม่รู้จัก
เริ่มที่ความเร็ว 0.75× พูดตามทีละประโยค แล้วกลับไปใช้ความเร็วปกติเมื่อเริ่มคล่อง
อัดเสียงตัวเองแล้วเทียบกับต้นฉบับ โดยสังเกตคำอย่าง edit, username, technique เป็นพิเศษ

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

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

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

ฝึกพูดภาษาอังกฤษด้วยเทคนิค Shadowing จากวิดีโอ: Spec-Driven Development: AI Assisted Coding Explained

What is Event Driven Architecture (EDA)?

What Is Jev? The AI Model That Doesn't Generate Text

AI, Machine Learning, Deep Learning and Generative AI Explained

AI Agents vs Business Rules: Which Should Make Decisions?

AI & Education: Generative AI & the Future of Critical Thinking

EDR vs. EPP vs. NGAV

MCP vs ADK: How Modern AI Agents Connect and Work Together

Cybersecurity Architecture: Data Security

The 7 Skills You Need to Build AI Agents

How Smart Organizations Will Use AI: Jevons Paradox & Workforce Impact

What are AI Agents?

Cybersecurity Architecture: Five Principles to Follow (and One to Avoid)

Zero Trust Explained in 4 mins

I've Changed My Opinion On DEVELOPERS Vibe Coding

FULL Data Science Mock Interview | SQL, Statistics, Business

Your AI broke the layout. Now what?

New Skills! v1.3 brings /pr, /implement-spec, and /retro

Is prompt engineering dead? Advice on optimizing AI interactions | Amazon Web Services

Design Patterns in Java Theory

Rapid Engineering With AI

How I use AI as a senior software engineer and 5 principles of AI explained in 10 minutes

Claude Code: The Advanced Guide (99% of Devs Skip These Features)

CS50x 2026 - Introduction

15 Minutes to Fix Your AI Dev Workflow with OpenCode

คำศัพท์และข้อสังเกตด้านการพูดสำหรับบทเรียนนี้

คำศัพท์สำคัญในวิดีโอนี้

กริยาวลีที่คุณจะได้ยิน

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

การออกเสียงที่ควรระวัง

วิธีฝึกกับวิดีโอนี้

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