跟讀練習: I've Changed My Opinion On DEVELOPERS Vibe Coding - 通過影片學習英語口語

選擇練習模式

每種模式都會開啟全屏練習室。

117 句

如果句子過短或過長，請點選 Edit 進行調整。

Hey guys, so I've been pretty vocal about Vibe Coding over the past year or so,

and most of what I've said has been pretty skeptical.

Watching people ship apps without understanding a single line of what was generated,

watching beginners get stuck the moment something broke,

and not to mention all the influencers pushing the idea

that you don't really have to know anything about software development to create successful apps and sasses,

which I'll never agree with.

However, I have changed my tune a little bit on Vibe Coding in general.

All right, so before we go any further,

let's define what Vibe Coding actually is,

because there's really a spectrum when it comes to coding with AI.

In fact, in my Coding with AI course,

I talk about five levels ranging from one-shot prompts with platforms like Lovable to just using autocomplete and VS Code.

And I think the sweet spot is right in the middle where you're letting the agent write the code,

but you're making the architectural decisions,

testing, writing spec files, etc. And that's what I teach in my AI course,

which I'll have the link for in the description if you're interested.

But to me, that's not vibe coding.

Vibe coding is where you're barely looking at the code at all.

And as the name implies,

you're kind of going off the vibes,

not the actual syntax, which is something that I've been totally against in the past.

However, over the past couple months or so,

I've been going all in with AI.

I've created a home lab with eight machines that's managed by my open claw Travis.

I have agents talking to each other,

assigning tasks and been creating all kinds of projects,

mostly things that I can use in my daily workflow.

So I've gotten a bit,

I guess, more liberal with just letting AI cook where before I would monitor and spec out every little feature.

The main reason that I've been able to kind of change my opinion on this is because of the models.

Opus 4.7 with Claude Code and GPT 5.5 with Codex

and even OpenClaw with GPT 5.5 are all amazing

if you understand how to direct these models to get the results that you want.

So I really don't think that we have to babysit the code as much as we did with,

for instance, GPT 5.3.

And I'm seeing much less hallucination.

And for the most part,

it does what I want on the first try.

Now, I know that some of that is because I've learned how to communicate with these models,

how to manage my context and memory,

how to map out my documentation and spec files.

So it doesn't mean that just anyone can can pick up any of these models and build a successful SaaS.

Which brings me to my main point,

I don't think vibe coding is okay under any circumstance if you don't have a foundation in software development and architecture.

So for instance, my mother,

who basically just only knows how to use Facebook,

will never be able to create a successful SaaS,

no matter how amazing the model gets,

unless she decides to learn software development,

which I know she's not.

And that's one thing I won't budge on and

if I do I want you guys to hold me to it

and I've seen this play out a hundred times you know

somebody with no real dev background uses an AI tool to build something in fact my accountant just did this

and told me about it

and had this exact experience they get version one in an afternoon

and they're thrilled version two is hotter version three breaks something in version one

and they don't know why and they ask the model to fix it

and the model makes it worse in a way that they can't see.

And now there are three layers deep in fixes that don't address the actual problem.

And the code base has architectural choices that nobody actually made on purpose.

And they can't even describe the bug clearly enough for the model to help.

So this is not a tooling problem.

It's a knowledge problem.

The user can't form the right mental model of what's happening because they never built the prerequisite intuition.

And no matter how good that model is,

it can only meet you where you are.

So even if it's smart enough to fix what's wrong,

you don't know where to tell it to look.

And even if it knows where to look and finds it on its own,

you can't understand the solution so that it doesn't happen again.

And that's only part of it, right?

There's a lot of technical skill that you need outside of just actual coding syntax.

Imagine vibe coding if you didn't understand Git or version control or didn't even know what it was.

If you didn't know how database tables work,

If you don't know how to set an environment variable,

you know, you don't even have the vocabulary to Vibecode.

And the agent is, it's going to be asking you stuff and asking you to make decisions that you don't understand.

And I haven't even mentioned deployment, maintenance, scaling.

That's all stuff that, that you need to know.

So with that said, you don't have to be a 20 year veteran software developer to use AI.

I think that people get frustrated with us sometimes because we say learn the fundamentals,

build a foundation, but what does that actually mean?

So foundation, at least in terms of a web development context,

it means understanding how the web works,

requests, responses, status codes, what happens between the browser and the server.

It means understanding data, how to model it,

how relationships work, what an index is it means

that you've written enough code by hand that you can read code and see it and not just skim past it.

And it means that you've been burned by enough bugs to recognize bad patterns.

You don't need a CS degree.

You don't need to memorize sorting algorithms or be a genius,

but you need to have built things from scratch,

debug them, broken them, fix them there's no shortcut to to

that pattern recognition and the model can't give

that to you the model can only really amplify what's already there

so with that said what should beginners do i wouldn't say stop using these tools these ai tools

that ship has sailed and honestly fighting it is is the wrong move in my opinion

100

but change what you're using them for use them to learn faster not skip learning.

101

AI is actually a really incredible tool for learning how to code and I don't feel like that's talked about enough.

102

In fact, me and my team are building on working on building a platform that merges AI with coding lessons.

103

But you can have the model explain the code that it generates,

104

type it out yourself, you know,

105

break it on purpose and try to figure out why it broke.

106

And the developers who are going to do well over the

107

next few years are not the ones who can prompt the best.

108

They're the ones who can prompt well and read code and design systems and debug under pressure.

109

The AI handles the typing.

110

You still have to handle the thinking.

111

And this is mainly towards beginners.

112

Back to vibe coding, once you get past that learning stage, vibe away.

113

However, don't make it the only way that you create

114

because you're going to forget a lot and depend on it too much.

115

So I'm not against vibe coding anymore.

116

I just think that it should be a tool,

117

not your entire workflow for every project.

下載應用

流利口語所需的一切

AI 發音評分逐句打分

音標練習掌握每個音

詞彙學習建立你的詞庫

詞彙遊戲邊玩邊學

掃碼

Download on theApp Store Get it onGoogle Play

同頻道

FOR YOU

為什麼要通過這個影片練習口語？

通過這個影片進行英語影子跟讀，能夠有效幫助學習者提升英語口語能力。影片中的講者不僅分享了對程式設計的觀點變化，還強調了與人工智慧互動的重要性。這種講述方式做到了生動且富有趣味，讓學習者能夠在放鬆的環境中吸收知識。因此，觀看和跟讀該影片可以讓你在掌握專業術語的同時，提高口語表達的流利度和自信心。通過對這些內容的反覆練習，能夠極大地改善你的英語口語練習效果。

語法和表達在語境中的運用

在這個影片中，講者使用了一些重要的語言結構，下面分析三到五個關鍵點：

“I have changed my opinion”: 使用了現在完成時，表明了他對某一觀點的變化，是表達個人成長和思考的重要方式。
“let the agent write the code”: 此句展示瞭如何利用自動化工具以及團隊合作的概念，強調了“授權”的重要性。
“understand how to direct these models”: 這是一個強調理解和引導的重要句型，反映出對成功溝通的需求。
“It doesn’t mean that just anyone can...”: 運用了條件句，表現出如沒有基礎知識就可能無法成功的論點。

掌握這些語法結構和表達方式，有助於提升自己的英語口語練習水平。

常見發音陷阱

在影片中的部分單詞和短語可能會對學習者造成發音上的困難。例如：

“Vibe Coding”: 這個短語包含了短母音和重音，初學者可能難以正確掌握其音調。
“software development”: 由於“development”中的重音和連音問題，初學者在發音時可能會出錯。
“models”: 字母“l”的發音可能會被忽略，導致發音不清晰。

通過不斷練習這些詞彙的發音，你將能夠提高英語發音的準確性。運用英語口語練習方法，例如影子跟讀，就是一個很好的提升發音的策略。

影片中的語法

說話人最常用的結構，並附上影片中的原話：

結構	影片中的用法
現在完成時 have/has + 過去分詞 — 過去發生但與現在仍有關聯的事	I've been · I've said · have changed
定語從句 who / which + 從句 — 補充說明人或事物	syntax, which is · ones who can
被動語態 be + 過去分詞 — 強調發生了什麼，而不是誰做的	was generated · you've been burned

什麼是跟讀法？

跟讀法 (Shadowing) 是一種有科學依據的語言學習技巧，最初開發用於專業口譯員的培訓，並由多語言者Alexander Arguelles博士普及。這個方法簡單而強大：您在聽英語母語原聲的同時立即大聲重複——就像是一個延遲1-2秒緊跟說話者的影子。與被動聽力或語法練習不同，跟讀法強迫您的大腦和口腔肌肉同時處理並模模擬實的講話模式。研究表明它能顯著提高發音準確性，語調，節奏，連讀，聽力理解和口語流利度——使其成為雅思口語備考和真實英語交流最有效的方法之一。

影子跟讀法: 閱讀完整分步指南 →

跟讀練習: I've Changed My Opinion On DEVELOPERS Vibe Coding - 通過影片學習英語口語

選擇練習模式

下載應用

同頻道

Does Anyone Use JavaScript Anymore?

Nobody is hiring vibe coders. Sorry

12 Important Concepts In the Age of AI Software Development

推薦影片

A Return to Code

My Vibe Coding Workflow (Step by Step Workflow)

FULL DISCUSSION: Google's Demis Hassabis, Anthropic's Dario Amodei Debate the World After AGI | AI1G

The 7 phases of AI-driven development

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

Modrinth Just BANNED AI Mods

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

World Models explained in 10min..

People Are Mad They're Told to Learn

Learning to code: How Pavel Durov learned to program | Lex Fridman Podcast Clips

mattpocock/skills: A complete AI Coding workflow, end-to-end

Everyone Is Wrong About AI Coding

為什麼要通過這個影片練習口語？

語法和表達在語境中的運用

常見發音陷阱

影片中的語法

什麼是跟讀法？