쉐도잉 연습: 7 Programming myths that waste your time - 영상으로 영어 말하기 배우기

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.

And most of that code is total garbage.

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.

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.

I wasted countless hours chasing programming dragons that made me feel more productive, but ultimately led nowhere.

In today's video, we'll debunk 9 smart ideas that waste your time as a programmer.

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.

Now, one of the main goals of this channel is to

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.

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,

Java runs most of the enterprise world, most databases are SQL-based, and C++ runs most of the low-level systems.

However, there are shiny new replacements for tech like this, including Next.js, Kotlin, NoSQL, and Rust.

And the lure is a massive feeling of FOMO if you're not mastering the bleeding edge of these so-called superior technologies.

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,

where the jobs exist, are not going to change their dinosaur tech stacks anytime soon.

The critical banking systems still run on COBOL, and Java will still be powering 3 billion devices long after everybody watching this is dead.

Most CTOs are smart enough to know that if it ain't broke, don't fix it.

Here's a real-life example.

A few years ago, engineers from Twitter released a hot new database called Fauna.

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.

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.

Adopting tech too early is one thing, but adhering to programming dogma can waste even more time.

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.

Some common cults out there include the object-oriented purists and the functional programming extremists.

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.

I mostly code in JavaScript, which is a multi-paradigm language that can satisfy all of these cults.

In 2018, functional programming was having a renaissance in web development.

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.

No mutable state and higher order functions everywhere.

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.

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.

Most of the advice in this book is great.

Use meaningful names, write small functions, use consistent formatting, and so on.

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.

And on the surface, that seems like a good idea.

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.

It's paralysis by analysis, and you end up spending more time refactoring than building actual features that people want.

I think a better acronym would be RUG, repeat until good.

Duplicate code at first and then pull it into a single abstraction after the repetition becomes painful.

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.

Your boss, who has no programming experience, is likely a big fan of code coverage tooling

that will show how much of your source code is executed when a test suite is run.

It's interesting, but optimizing for 100% coverage is often a huge waste of time

and can often be misleading because high coverage does not equal high quality.

Optimizing for coverage encourages developers to write pointless tests that just touch lines and not catch real bugs.

And even worse than wasting time, it provides a full sense of security.

And then on top of that, it makes your CI builds even slower, which is going to cost you more money.

When it comes to test coverage, it's quality, not quantity, that matters.

But one thing that truly must matter is performance.

Well, actually, it's a myth that you should always optimize for performance.

Yet another time waster is benchmarking and optimizing code that just doesn't run at the scale to justify those optimizations.

It's far more important to make sure that your code is correct

and then only optimize for performance when it becomes painfully obvious that your code sucks in production.

On a similar note, you also don't need to optimize your cloud infrastructure like you're about to scale like Facebook.

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.

Then finally, that brings us to the elephant in the room, the myth that AI is about to replace all programmers soon.

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.

For example, Claude Sonnet 3.7 is really good at writing code, but it's also notoriously verbose.

You might ask it to build a simple website, and it'll just randomly engineer some new JavaScript framework from scratch.

And because you forgot how to write code, you'll just approve it and move on with your life.

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.

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.

A hard truth is that code is useless if you don't understand the math and computer science behind it.

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.

But most importantly, you'll build critical thinking skills through problem solving, not memorizing.

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.

Try everything Brilliant has to offer for free for 30 days by visiting brilliant.org slash fireship

or scan the QR code on screen and get 20% off an annual premium subscription.

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

📺 같은 채널

✨ 추천 영상

225 문장

If You Only Watch One Video Today, Make It This One

Business EnglishUniversity StudentsWorking Adults

12 문장

How I’d Learn Coding in 2026 (Without Wasting Years)

Business EnglishUniversity StudentsWorking Adults

190 문장

He’s always wrong

Business EnglishDaily ConversationUniversity Students

103 문장

Wild times we live in

Business EnglishUniversity StudentsWorking Adults

261 문장

I don't like Programming

Business EnglishUniversity StudentsWorking Adults

49 문장

AI & Future Jobs: Skills You NEED Now!

Business EnglishUniversity StudentsWorking Adults

781 문장

How Do I Reverse Brain Rot?

Business EnglishUniversity StudentsWorking Adults

260 문장

9 Investments for Better Learning

Business EnglishUniversity StudentsWorking Adults

55 문장

Cloud Providers are changing RAPIDLY [REUPLOAD]

Business EnglishUniversity StudentsWorking Adults

126 문장

Therapy for the Vibe-Coded Brain

Business EnglishUniversity StudentsWorking Adults

이 레슨의 어휘와 말하기 포인트

이 영상에는 섀도잉할 문장 69개와 단어 1366개가 있습니다. 말하는 구간의 길이는 6:18입니다. 화자는 분당 약 217단어로 빠르게 말하므로 연음과 약하게 발음되는 소리가 많습니다. 영어에서 가장 많이 쓰이는 3,000단어에 속하는 단어가 80%뿐이라 어휘가 어려운 편입니다.

이 영상의 핵심 어휘

영상에 나오는 덜 흔한 단어 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.
server /ˈsɝvɚ/ (명사) — 서버, 봉사기. A program that provides services to other programs or devices, either in the same computer or over a computer network.
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.
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.
superior /sʊˈpɪɹ.i.ɚ/ (형용사) — 우수한. Higher in rank, status, or quality.
encourage /ɪnˈkʌɹ.ɪd͡ʒ/ (동사) — 격려하다. To mentally support; to motivate, give courage, hope or spirit.
chase /t͡ʃeɪs/ (동사) — 쫓다. To follow at speed.
architecture /ˈɑː.kɪˌtɛk.t͡ʃə/ (명사) — 건축, 건축학. The art and science of designing and managing the construction of buildings and other structures, particularly if they are well proportioned and decorated.

주의할 발음

화자는 don't, I've, you'll 같은 축약형과 약화된 형태를 24번 사용합니다. 들리는 대로 짧게 발음하세요.

“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/

이 영상으로 연습하는 방법

먼저 말하지 않고 영상을 끝까지 듣고 모르는 단어를 적어 둡니다.
0.75배속으로 한 문장씩 섀도잉을 시작하고, 익숙해지면 보통 속도로 돌아갑니다.
자신의 목소리를 녹음해 원본과 비교하고, 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)은 원래 전문 통역사 훈련을 위해 개발된 언어 학습 기법으로, 다언어 학자인 Dr. Alexander Arguelles에 의해 대중화된 방법입니다. 핵심 원리는 간단하지만 매우 강력합니다: 원어민의 영어를 들으면서 1~2초의 짧은 지연으로 즉시 소리 내어 따라 말하는 것——마치 '그림자(shadow)'처럼 화자를 따라가는 것입니다. 문법 공부나 수동적인 청취와 달리, 쉐도잉은 뇌와 입 근육이 동시에 실시간으로 영어를 처리하고 재현하도록 훈련합니다. 연구에 따르면 이 방법은 발음 정확도, 억양, 리듬, 연음, 청취력, 말하기 유창성을 크게 향상시킵니다. IELTS 스피킹 준비와 자연스러운 영어 소통을 원하는 분들에게 특히 효과적입니다.

섀도잉 방법: 단계별 전체 가이드 읽기 →

쉐도잉 연습: 7 Programming myths that waste your time - 영상으로 영어 말하기 배우기

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

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

7 Things No Programmer Ever Wants to Hear

80% of programmers are NOT happy… why?

The most interesting hack in history just got weirder...

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…

If You Only Watch One Video Today, Make It This One

How I’d Learn Coding in 2026 (Without Wasting Years)

He’s always wrong

Wild times we live in

I don't like Programming

AI & Future Jobs: Skills You NEED Now!

How Do I Reverse Brain Rot?

9 Investments for Better Learning

Cloud Providers are changing RAPIDLY [REUPLOAD]

Therapy for the Vibe-Coded Brain

이 레슨의 어휘와 말하기 포인트

이 영상의 핵심 어휘

주의할 발음

이 영상으로 연습하는 방법

이 영상의 문법

쉐도잉이란? 영어 실력을 빠르게 키우는 과학적 방법