跟读练习: 7 Things No Programmer Ever Wants to Hear - 通过视频学习英语口语

Being a software engineer sucks.

I was told I would be working in a fast-paced, exciting environment, but in reality, I'm stuck in this cubicle, building super complex stuff that nobody understands or appreciates.

If I had a time machine, I would do two things.

One, I would tell Harambe to get away from that kid.

NOOOOO!

And two, I would go back to school to become a civil engineer, so I could work outside building stuff everyone admires, like bridges and skyscrapers.

Unfortunately, I haven't figured out how to build a time machine in JavaScript yet.

Now, I would never recommend anybody choose software engineering as a career, but if you do make bad life choices like me, you should be prepared for some really bad things to happen.

Like, every doctor eventually loses a patient, and every pilot eventually crashes a plane.

Likewise, every software engineer will eventually face a merge conflict, and that's not even very bad.

In today's video, we'll look at 7 different devastating text messages that no developer ever wants to hear.

Speaking of which, I finally started a Discord, so feel free to chat with me over there after this video.

We've got some t-shirts and licenses to JetBrains software to give away over there.

One of the biggest problems with software engineering is

that you don't want your friends and family to find out what you do.

The reason is you'll get messages like this from your uncle

or old roommate asking if you want to build an app together.

It will consist of a very dumb idea that's impossibly complex to execute, like Uber but for horses, or TikTok without the Chinese, with a $500 budget.

Messages like this are so painful

because software engineers are usually introverts who have a hard time saying no. What you'll wanna do is respond and say, hey, that's an awesome idea.

I would love to build it for you, but my rate is $300 an hour.

What they'll likely do is come back with a counter offer of $0 per hour, but 10% equity in the company, which will eventually be worth billions.

That's pretty much checkmate.

Check speaks for itself.

I would just recommend accepting the offer and building the app to get them to go away.

Now, when you're not building apps for friends and family, you should be working on your own side projects.

And in doing that, you'll likely use the cloud like AWS.

One of the worst messages you can receive is a cloud billing alert like, Hey, it's AWS.

Your $25 budget has been exceeded by $2.3 million.

Maybe you clicked the wrong button or accidentally created an infinite loop, but the important thing here is not to panic.

The easiest solution is to just stop using AWS and pretend nothing ever happened.

If Jeff ever sends his guys after you, just tell them your account got hacked.

That may or may not work, and

if it doesn't, you can at least find comfort in knowing there are many

other homeless people out there who simply forgot to turn off an EC2 instance.

Another dreaded, catastrophic thing a developer doesn't want to hear is that a production database has been dropped accidentally, along with all of your company's data that was worth billions of dollars.

You just made the simple mistake of dropping prod instead of dev.

When something like this happens, it's absolutely terrifying, but hopefully you have backups that are able to restore it back to its original state.

If not, now would be a good time to start looking for a new job.

Dropping a database is incredibly easy and can be accomplished with a single line of code.

You can use this knowledge to fight back against the system, as this person did here, by weaponizing SQL injection against speed cameras.

Dropping a database is bad, but at least it's over quickly.

Many developers suffer a worse fate, like this guy who got a message from his boss, assigning him to a legacy AngularJS version 1 codebase that needs to be migrated to Angular 14.

Sadly, the previous developer died of old age, and was the only one who had any idea how anything in this codebase worked.

He knew exactly how to keep his job by creating an overly complex codebase without any comments or documentation, and now it's your turn to update it.

Fuck my life.

This job will take more skill and ingenuity than building a nuclear submarine, and when you finally finish the job in a few years, no one will even notice or care,

because by that time it'll be time to migrate your legacy codebase into the hot new JavaScript framework of 2025.

Speaking of which, something a web developer never wants to hear is that a new, better JavaScript framework has been invented.

When you learn a JavaScript framework, you join a tribe, and that means everything outside that tribe is dangerous and terrible.

Now normally, you can create an echo chamber to convince yourself

that your chosen framework is absolutely 100% the best in every use case.

However, at some point, you may be convinced that a better framework does in fact exist.

When that day comes, you'll need to turn your back on your tribe and lose many friends in the process.

And it's not exactly easy to make new friends when you're a software engineer.

I can't sit here.

But one of the most annoying things that can happen to you is when a non-technical person, like a client or marketing expert, asks you to make one small change to an already finished product.

Like, let's just move this nav bar from the top over to the side here.

It should be an easy change for you to make.

You don't not want to look like a 10x developer, so you go ahead and do it, But it takes like 20 hours and modifications in a hundred different HTML and CSS files.

Then as soon as you commit your work, that same person will come back and say, you know what, I think I liked it better the first way.

Let's go ahead and change it back.

It's no secret that the most important skill of a software engineer is being able to Google things effectively.

That means one of the worst things

that can happen to you is running into a problem that nobody else has already solved for you.

It's painful enough when zero results come back on Google with your error message, but an even worse thing can happen.

You might search an error and get a single result on an obscure forum from 10 years ago, and find some dude going through the exact same problem as you.

As you scroll down, hoping for a well-documented and detailed solution, you find that all he posted was fixed, all good now.

And now you have to figure out the problem all by yourself.

Being the Chad that you are, you get to work, and as soon as you're about to solve the problem, you get a notification that it's time for your daily stand-up meeting.

Thanks for watching, and I will see you in the next one.

📺 同频道

✨ 推荐视频

751 句

7 Conversations Every Ambitious Person Needs to Hear | Dear Leila

Business EnglishDaily ConversationUniversity Students

175 句

I Gave the MIT Commencement Speech

Business EnglishDaily ConversationUniversity Students

583 句

Episode 531: Shallow feedback and my coworker is a huge sloperator

Business EnglishUniversity StudentsWorking Adults

202 句

SOFTWARE ENGINEER Interview Questions & TOP SCORING ANSWERS!

Business EnglishInterview EnglishUniversity Students

125 句

Practical Advice for Creative Projects - Extra Credits Gaming

Business EnglishUniversity StudentsWorking Adults

169 句

Can This Vibe Coder Beat a Senior Developer?

Business EnglishUniversity StudentsWorking Adults

208 句

Graphic Designers Were Trained to Be Replaceable

Business EnglishUniversity StudentsWorking Adults

21 句

Business is Hard Until You Design it Like This

Business EnglishWorking Adults

278 句

AI Food Slop is Here

Business EnglishUniversity StudentsWorking Adults

63 句

How To Land Your First Junior Dev Role

Business EnglishInterview EnglishUniversity Students

本课的词汇与口语要点

这段视频共有 71 个句子、1208 个单词可供跟读。讲话部分时长为 5:14。说话人语速较快，每分钟约 231 个词，会出现较多连读和弱读。 83% 的单词属于英语最常用的 3,000 词，其余的词建议在练习前先学一下。

视频中的重点词汇

视频中 15 个值得学习的单词，附发音和释义：

单词	发音	释义
framework 名词	/ˈfɹeɪm.wɜːk/	骨架, 框架
database 名词	/ˈdeɪtəˌbeɪs/	數據庫 /数据库
cloud 名词	/ˈklaʊ̯d/	йүн, 雲 /云
skill 名词	/skɪl/	技巧, 技能
solve 动词	/sɒlv/	解決 /解决
legacy 名词	/ˈlɛɡəsi/	遺產 /遗产
painful 形容词	/ˈpeɪn.fl̩/	痛苦的, 疼痛的
convince 动词	/kənˈvɪns/	說服 /说服
accidentally 副词	/ˌæk.sɪˈdɛnt(ə)li/	偶然
chamber 名词	/ˈt͡ʃeɪ̯mbɚ/	臥室 /卧室, 寢室 /寝室
suffer 动词	/ˈsʌfɚ/	受苦, 遭受
uncle 名词	/ˈʌŋ.kl̩/	伯父, 伯伯
suck 动词	/sʌk/	吸吮, 咂
comfort 名词	/ˈkʌm.fət/	舒適 /舒适
forum 名词	/ˈfɔːɹəm/	論壇 /论坛, 座談會 /座谈会

视频中出现的短语动词

单词	发音	释义
figure out 动词		弄清楚
go ahead 动词	/ˌɡoʊ əˈhɛd/	請便 /请便
come back 动词		回來 /回来, 返回
find out 动词		找出, 查明
go away 动词		離開 /离开, 走
go through 动词		通過 /通过
stand up 动词		站起來 /站起来, 起來 /起来
turn off 动词		關 /关, 關掉 /关掉

视频中的语法

说话人最常用的结构，并附上视频中的原话：

结构	视频中的用法
条件句 if + 从句，will/would + 动词 — 条件及其结果	If not, now would be
被动语态 be + 过去分词 — 强调发生了什么，而不是谁做的	was told · should be prepared · has been exceeded
现在完成时 have/has + 过去分词 — 过去发生但与现在仍有关联的事	haven't figured · has been exceeded · has been dropped
定语从句 who / which + 从句 — 补充说明人或事物	company, which will · guy who got · one who had

需要注意的发音

说话人用了 19 次缩略和弱读形式，例如 you'll, you're, doesn't。请按听到的简短形式来说。

“sh” 和 “zh” 音: accomplish /əˈkɑm.plɪʃ/, injection /ɪnˈd͡ʒɛk.ʃən/, documentation /ˌdɑkjəmɛnˈteɪʃən/, notification /ˌnoʊtɪfɪˈkeɪʃn̩/, modification /ˌmɑdɪfɪˈkeɪʃən/
长单词——注意重音位置: developer /dɪˈvɛləpɚ/, accidentally /ˌæk.sɪˈdɛnt(ə)li/, incredibly /ɪŋˈkɹɛdɪbli/, documentation /ˌdɑkjəmɛnˈteɪʃən/, notification /ˌnoʊtɪfɪˈkeɪʃn̩/

如何用这段视频练习

先完整听一遍视频，不要开口，记下不认识的单词。
先用 0.75 倍速逐句跟读，熟练之后再回到正常速度。
录下自己的声音并与原声对比，特别注意 framework, database, cloud 这类单词。

什么是跟读法？

跟读法 (Shadowing) 是一种有科学依据的语言学习技巧，最初开发用于专业口译员的培训，并由多语言者Alexander Arguelles博士普及。这个方法简单而强大：您在听英语母语原声的同时立即大声重复——就像是一个延迟1-2秒紧跟说话者的影子。与被动听力或语法练习不同，跟读法强迫您的大脑和口腔肌肉同时处理并模仿真实的讲话模式。研究表明它能显着提高发音准确性，语调，节奏，连读，听力理解和口语流利度——使其成为雅思口语备考和真实英语交流最有效的方法之一。

影子跟读法: 阅读完整分步指南 →

跟读练习: 7 Things No Programmer Ever Wants to Hear - 通过视频学习英语口语

10 very promising Open Source Projects you haven’t heard of

7 Programming myths that waste your time

DHH has gone completely off the rails...

DNS Explained in 100 Seconds

Anthropic begged the world to stop AI… then shipped this

One man just liberated Fable... and now it’s illegal

80% of programmers are NOT happy… why?

Raspberry Pi Explained in 100 Seconds

Did Google just kickstart the intelligence explosion?

Tragic mistake... Anthropic leaks Claude’s source code

100+ Docker Concepts you Need to Know

When open-sourcing your code goes wrong...

Docker in 100 Seconds

The mystery is solved... and the answer is 40x cheaper than Claude

An ex-OpenAI researcher just deleted language from the LLM...

25 crazy software bugs explained

Git Explained in 100 Seconds

There's a new Linux distro in town for developers...

The "vibe coding" mind virus explained…

Linux got wrecked by backdoor attack

7 Conversations Every Ambitious Person Needs to Hear | Dear Leila

I Gave the MIT Commencement Speech

Episode 531: Shallow feedback and my coworker is a huge sloperator

SOFTWARE ENGINEER Interview Questions & TOP SCORING ANSWERS!

Practical Advice for Creative Projects - Extra Credits Gaming

Can This Vibe Coder Beat a Senior Developer?

Graphic Designers Were Trained to Be Replaceable

Business is Hard Until You Design it Like This

AI Food Slop is Here

How To Land Your First Junior Dev Role

本课的词汇与口语要点

视频中的重点词汇

视频中出现的短语动词

视频中的语法

需要注意的发音

如何用这段视频练习

什么是跟读法？