शैडोइंग अभ्यास: 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.

📺 उसी चैनल से

A $6.3 billion open-weight model just got embarrassed by the French...

✨ अनुशंसित वीडियो

26 वाक्य

Two Developers Before a Release: The Login Bug Is Back

Business EnglishDaily ConversationWorking Adults

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

542 वाक्य

The Future Of Work (& The New High-Income Skill Stack)

Business EnglishUniversity StudentsWorking Adults

31 वाक्य

Job Interview: Software Developer at a Startup

Business EnglishInterview EnglishWorking Adults

12 वाक्य

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

Business EnglishUniversity StudentsWorking Adults

125 वाक्य

Practical Advice for Creative Projects - Extra Credits Gaming

Business EnglishUniversity StudentsWorking Adults

201 वाक्य

Every Level of Engineering in 15 Minutes

Business EnglishUniversity StudentsWorking Adults

522 वाक्य

Episode 533: I'm drowning in AI slop from lazy coworkers

Business EnglishUniversity StudentsWorking Adults

21 वाक्य

Business is Hard Until You Design it Like This

Business EnglishWorking Adults

इस पाठ की शब्दावली और बोलने के सुझाव

इस वीडियो में शैडोइंग के लिए 71 वाक्य और 1208 शब्द हैं। बोला गया हिस्सा 5:14 लंबा है। वक्ता तेज़ बोलता है, लगभग 231 शब्द प्रति मिनट, इसलिए जुड़ी हुई और कमज़ोर ध्वनियाँ ज़्यादा मिलेंगी। 83% शब्द अंग्रेज़ी के 3,000 सबसे आम शब्दों में से हैं; बाकी शब्द अभ्यास से पहले देख लेना अच्छा रहेगा।

इस वीडियो की मुख्य शब्दावली

वीडियो के 15 सीखने लायक शब्द, उच्चारण और अर्थ के साथ:

शब्द	उच्चारण	अर्थ
developer संज्ञा	/dɪˈvɛləpɚ/	विकासक
database संज्ञा	/ˈdeɪtəˌbeɪs/	डेटाबेस
cloud संज्ञा	/ˈklaʊ̯d/	मेघ, बादल
skill संज्ञा	/skɪl/	कुशलता, कौशल
solve क्रिया	/sɒlv/	सुलझाना, हल करना
painful विशेषण	/ˈpeɪn.fl̩/	दुखदायी, दुखद
chamber संज्ञा	/ˈt͡ʃeɪ̯mbɚ/	शयनकक्ष
uncle संज्ञा	/ˈʌŋ.kl̩/	चाचा, ताऊ
suck क्रिया	/sʌk/	चूसना
comfort संज्ञा	/ˈkʌm.fət/	आराम, सुखद
fate संज्ञा	/feɪt/	क़िस्मत, किस्मत
alert विशेषण	/əˈlɝt/	सतर्क, सजग
pretend क्रिया	/pɹəˈtɛnd/	ढोंग
loop संज्ञा	/luːp/	कुंडली
panic संज्ञा	/ˈpænɪk/	संत्रास, आतंक

वीडियो में आने वाली फ़्रेज़ल वर्ब

शब्द	उच्चारण	अर्थ
go ahead क्रिया	/ˌɡoʊ əˈhɛd/	आगे बढ़ना
come back क्रिया		वापस आना
stand up क्रिया		उठना
turn off क्रिया		बंद करना

इस वीडियो का व्याकरण

वक्ता जिन संरचनाओं का सबसे अधिक प्रयोग करता है, वीडियो के असली शब्दों के साथ:

संरचना	वीडियो में
शर्त वाले वाक्य if + उपवाक्य, will/would + क्रिया — शर्त और उसका नतीजा	If not, now would be
Passive voice be + past participle — ज़ोर इस पर कि क्या होता है, न कि कौन करता है	was told · should be prepared · has been exceeded
Present perfect have/has + past participle — बीता हुआ काम जिसका असर अभी भी है	haven't figured · has been exceeded · has been dropped
Relative clauses 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× गति से शुरू करें, एक-एक वाक्य की शैडोइंग करें, और सहज लगने पर सामान्य गति पर लौटें।
अपनी आवाज़ रिकॉर्ड करें और मूल से तुलना करें, ख़ासकर developer, database, cloud जैसे शब्दों पर ध्यान दें।

शैडोइंग तकनीक क्या है?

शैडोइंग (Shadowing) एक विज्ञान-समर्थित भाषा सीखने की तकनीक है जो मूल रूप से पेशेवर दुभाषिया प्रशिक्षण के लिए विकसित की गई थी। विधि सरल लेकिन शक्तिशाली है: आप मूल अंग्रेज़ी ऑडियो सुनते हैं और तुरंत इसे ज़ोर से दोहराते हैं — जैसे वक्ता की छाया 1-2 सेकंड की देरी से। शोध से पता चलता है कि यह उच्चारण सटीकता, स्वर, लय, जुड़ी हुई ध्वनियाँ, सुनने की समझ और बोलने की प्रवाहशीलता में काफ़ी सुधार करता है।

शैडोइंग तकनीक: पूरी चरण-दर-चरण गाइड पढ़ें →

शैडोइंग अभ्यास: 7 Things No Programmer Ever Wants to Hear - वीडियो के साथ अंग्रेजी बोलना सीखें

A $6.3 billion open-weight model just got embarrassed by the French...

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

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 Programming myths that waste your time

Two Developers Before a Release: The Login Bug Is Back

7 Conversations Every Ambitious Person Needs to Hear | Dear Leila

I Gave the MIT Commencement Speech

The Future Of Work (& The New High-Income Skill Stack)

Job Interview: Software Developer at a Startup

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

Practical Advice for Creative Projects - Extra Credits Gaming

Every Level of Engineering in 15 Minutes

Episode 533: I'm drowning in AI slop from lazy coworkers

Business is Hard Until You Design it Like This

इस पाठ की शब्दावली और बोलने के सुझाव

इस वीडियो की मुख्य शब्दावली

वीडियो में आने वाली फ़्रेज़ल वर्ब

इस वीडियो का व्याकरण

ध्यान देने योग्य उच्चारण

इस वीडियो से अभ्यास कैसे करें

शैडोइंग तकनीक क्या है?