跟读练习: 7 Programming myths that waste your time - 通过视频学习英语口语

选择练习模式

每种模式都会打开全屏练习室。

69 句
如果句子过短或过长,请点击 Edit 进行调整。
1
Recently, I unlocked a new achievement in life, a midlife crisis, when I came to the realization that I've spent most of my adult life writing code.
2
And most of that code is total garbage.
3
It's code that never saw the light of a production server and was either abandoned, refactored, or left to rot in the graveyard of GitHub.
4
As I reflected upon this further, I realized that many of the best practices, the hot game-changing frameworks, and the perfect folder structures didn't actually matter to the end user.
5
I wasted countless hours chasing programming dragons that made me feel more productive, but ultimately led nowhere.
6
In today's video, we'll debunk 9 smart ideas that waste your time as a programmer.
7
And for each myth, we'll look at how it lures you in, why it's actually a trap, and most importantly, how to not do the things that I have done.
8
Now, one of the main goals of this channel is to
9
show you the latest tech you need to use to be relevant, but it's actually a myth that you need to use the latest tech to be relevant.
10
In fact, you might even become more hireable by focusing on old dinosaur technologies, like WordPress and PHP still runs most of the web applications out there,
11
Java runs most of the enterprise world, most databases are SQL-based, and C++ runs most of the low-level systems.
12
However, there are shiny new replacements for tech like this, including Next.js, Kotlin, NoSQL, and Rust.
13
And the lure is a massive feeling of FOMO if you're not mastering the bleeding edge of these so-called superior technologies.
14
To be clear, I'm not discouraging you from learning these, they're awesome, but it's important to understand that most of the real world,
15
where the jobs exist, are not going to change their dinosaur tech stacks anytime soon.
16
The critical banking systems still run on COBOL, and Java will still be powering 3 billion devices long after everybody watching this is dead.
17
Most CTOs are smart enough to know that if it ain't broke, don't fix it.
18
Here's a real-life example.
19
A few years ago, engineers from Twitter released a hot new database called Fauna.
20
It was a pretty solid product and I even made a video about it, but the technology was proprietary, VC-funded, and like most startups, the business failed recently.
21
They have no choice but to shut down their servers, and if you were an early adopter, you're now screwed, and would have been much better off with a boring SQL database.
22
Adopting tech too early is one thing, but adhering to programming dogma can waste even more time.
23
The problem with programming is that there are many different ways to solve the same problem, but some people out there believe that there's only one true way to write code.
24
Some common cults out there include the object-oriented purists and the functional programming extremists.
25
I've been a member of both cults and have learned a lot from them, but dedicating your entire life to just one of them is a waste of time.
26
I mostly code in JavaScript, which is a multi-paradigm language that can satisfy all of these cults.
27
In 2018, functional programming was having a renaissance in web development.
28
Back then, if you used classes in your code, you were literally Hitler, and I found myself bending over backwards to try to do everything in the most functional way possible.
29
No mutable state and higher order functions everywhere.
30
But a few years later, after the spell wore off, I eventually realized that classes can be pretty useful, and my code today often includes a combination of things I've learned from both of these cults.
31
But another time waster to watch out for is Clean Code, which comes from a legendary book written by Uncle Bob Martin known as the Handbook for Agile Software Craftsmanship.
32
Most of the advice in this book is great.
33
Use meaningful names, write small functions, use consistent formatting, and so on.
34
But some of the advice is a little more nuanced, like the dry principle of don't repeat yourself, which means you shouldn't duplicate or write the same code over and over again.
35
And on the surface, that seems like a good idea.
36
But also when you try too hard to keep things clean, you might end up with an endless layer of wrappers, interfaces, and pointless indirection.
37
It's paralysis by analysis, and you end up spending more time refactoring than building actual features that people want.
38
I think a better acronym would be RUG, repeat until good.
39
Duplicate code at first and then pull it into a single abstraction after the repetition becomes painful.
40
Clean code also recommends test-driven development, and testing can be extremely valuable, but it's a myth that 100% test coverage means that your code is well protected.
41
Your boss, who has no programming experience, is likely a big fan of code coverage tooling
42
that will show how much of your source code is executed when a test suite is run.
43
It's interesting, but optimizing for 100% coverage is often a huge waste of time
44
and can often be misleading because high coverage does not equal high quality.
45
Optimizing for coverage encourages developers to write pointless tests that just touch lines and not catch real bugs.
46
And even worse than wasting time, it provides a full sense of security.
47
And then on top of that, it makes your CI builds even slower, which is going to cost you more money.
48
When it comes to test coverage, it's quality, not quantity, that matters.
49
But one thing that truly must matter is performance.
50
Well, actually, it's a myth that you should always optimize for performance.
51
Yet another time waster is benchmarking and optimizing code that just doesn't run at the scale to justify those optimizations.
52
It's far more important to make sure that your code is correct
53
and then only optimize for performance when it becomes painfully obvious that your code sucks in production.
54
On a similar note, you also don't need to optimize your cloud infrastructure like you're about to scale like Facebook.
55
Like, I used to think that I needed this complex, serverless, microservice architecture with global sharding and edge caching, but it turns out that one small VPS is perfectly fine for my five users.
56
Then finally, that brings us to the elephant in the room, the myth that AI is about to replace all programmers soon.
57
There's some awesome AI code writing tools out there, but it's becoming more and more clear that many programmers are now wasting a bunch of time relying too much on AI.
58
For example, Claude Sonnet 3.7 is really good at writing code, but it's also notoriously verbose.
59
You might ask it to build a simple website, and it'll just randomly engineer some new JavaScript framework from scratch.
60
And because you forgot how to write code, you'll just approve it and move on with your life.
61
AI programming tools are both the greatest productivity booster I've ever seen in my life, but when used improperly, they can also be the biggest time waster.
62
The key to success is to have a solid foundation in problem solving, and you can start building that foundation for free today thanks to this video's sponsor, Brilliant.
63
A hard truth is that code is useless if you don't understand the math and computer science behind it.
64
Brilliant helps you learn these concepts quickly by providing short, fun, interactive lessons, which is a method proven to be six times more effective than watching video lectures.
65
But most importantly, you'll build critical thinking skills through problem solving, not memorizing.
66
Before you try to jump into vibe coding, I'd highly recommend taking their thinking and code course to build a timeless problem solving foundation, where you'll learn how to actually think like a programmer.
67
Try everything Brilliant has to offer for free for 30 days by visiting brilliant.org slash fireship
68
or scan the QR code on screen and get 20% off an annual premium subscription.
69
Thanks for watching and I will see you in the next one.

下载应用

流利口语所需的一切

AI 发音评分逐句打分
音标练习掌握每个音
词汇学习建立你的词库
词汇游戏边玩边学

同频道

FOR YOU

推荐视频

本课的词汇与口语要点

这段视频共有 69 个句子、1366 个单词可供跟读。 讲话部分时长为 6:18。 说话人语速较快,每分钟约 217 个词,会出现较多连读和弱读。 只有 80% 的单词属于英语最常用的 3,000 词,词汇难度较高。

视频中的重点词汇

视频中 15 个不太常见的单词,附发音和释义:

  • myth /mɪθ/ (名词) — 迷思. A traditional story which embodies a belief regarding some fact or phenomenon of experience, and in which often the forces of nature and of the soul are…
  • solve /sɒlv/ (动词) — 解決 /解决. To find an answer or solution to a problem or question; to work out.
  • programmer /ˈpɹoʊɡɹæmɚ/ (名词) — 程序員 /程序员, 程式員 /程式员. One who writes computer programs.
  • database /ˈdeɪtəˌbeɪs/ (名词) — 數據庫 /数据库. A collection of (usually) organized information in a regular structure, usually but not necessarily in a machine-readable format accessible by a computer.
  • functional /ˈfʌŋkt͡ʃənəl/ (形容词) — 功能的. In good working order.
  • server /ˈsɝvɚ/ (名词) — 服務器 /服务器, 伺服器. A program that provides services to other programs or devices, either in the same computer or over a computer network.
  • framework /ˈfɹeɪm.wɜːk/ (名词) — 骨架, 框架. A support structure comprising joined parts or conglomerated particles and intervening open spaces of similar or larger size.
  • importantly /ɪmˈpɔɹ.tənt.li/ (副词) — 重要的是.... Used to mark a statement as having importance.
  • dinosaur /ˈdaɪnəsoɹ/ (名词) — 恐龍 /恐龙. Those animals of the clade Dinosauria that existed during the Triassic, Jurassic and Cretaceous periods and are now extinct.
  • duplicate /ˈd(j)uː.plɪˌkeɪt/ (动词) — 複製 /复制. To make a copy of.
  • consistent /kənˈsɪs.tənt/ (形容词) — 一貫的 /一贯的. Of a regularly occurring, dependable nature.
  • format /ˈfɔːɹ.mæt/ (名词) — 格式, 開本 /开本. The layout of a publication or document.
  • lesson /ˈlɛs.ən/ (名词) — 課業 /课业, -課 /-课. A section of learning or teaching into which a wider learning content is divided.
  • cloud /ˈklaʊ̯d/ (名词) — йүн, 雲 /云. A visible mass of water droplets suspended in the air.
  • infrastructure /ˈɪnfɹəˌstɹʌkt͡ʃə/ (名词) — 基礎設施 /基础设施. An underlying base or foundation for a building, organization, or system.

视频中出现的短语动词

  • come from (动词) — 來自 /来自. To have as one's origin, birthplace or nationality.
  • end up (动词) — 到达. To bring to a conclusion.
  • look at (动词) — 觀察 /观察, 看. To observe or watch.
  • turn out (动词) — 原來 /原来. To end up; to result.

需要注意的发音

说话人用了 24 次缩略和弱读形式,例如 don't, I've, you'll。请按听到的简短形式来说。

  • “th” 音: myth /mɪθ/, mathematics /mæθ(.ə)ˈmæt.ɪks/
  • “sh” 和 “zh” 音: subscription /səbˈskɹɪpʃən/, realization /ˌɹɪə.laɪˈzeɪ.ʃən/, optimization /ˌɑptəmaɪˈzeɪʃən/, cache /kæʃ/, benchmark /ˈbɛn(t)ʃmɑːk/
  • 长单词——注意重音位置: importantly /ɪmˈpɔɹ.tənt.li/, infrastructure /ˈɪnfɹəˌstɹʌkt͡ʃə/, superior /sʊˈpɪɹ.i.ɚ/, architecture /ˈɑː.kɪˌtɛk.t͡ʃə/, legendary /ˈlɛd͡ʒ.ənˌdɛɹ.i/

如何用这段视频练习

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

视频中的语法

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

结构视频中的用法
现在完成时 have/has + 过去分词 — 过去发生但与现在仍有关联的事I've spent · have done · I've been
定语从句 who / which + 从句 — 补充说明人或事物JavaScript, which is · yourself, which means · slower, which is

什么是跟读法?

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

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