Shadowing Practice: 7 Things No Programmer Ever Wants to Hear - Learn English Speaking with Video

בחר מצב תרגול

כל מצב פותח חדר תרגול במסך מלא.

71 משפטים
אם המשפטים קצרים או ארוכים מדי, לחץ על ערוך כדי להתאים אותם.
1
Being a software engineer sucks.
2
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.
3
If I had a time machine, I would do two things.
4
One, I would tell Harambe to get away from that kid.
5
NOOOOO!
6
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.
7
Unfortunately, I haven't figured out how to build a time machine in JavaScript yet.
8
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.
9
Like, every doctor eventually loses a patient, and every pilot eventually crashes a plane.
10
Likewise, every software engineer will eventually face a merge conflict, and that's not even very bad.
11
In today's video, we'll look at 7 different devastating text messages that no developer ever wants to hear.
12
Speaking of which, I finally started a Discord, so feel free to chat with me over there after this video.
13
We've got some t-shirts and licenses to JetBrains software to give away over there.
14
One of the biggest problems with software engineering is
15
that you don't want your friends and family to find out what you do.
16
The reason is you'll get messages like this from your uncle
17
or old roommate asking if you want to build an app together.
18
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.
19
Messages like this are so painful
20
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.
21
I would love to build it for you, but my rate is $300 an hour.
22
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.
23
That's pretty much checkmate.
24
Check speaks for itself.
25
I would just recommend accepting the offer and building the app to get them to go away.
26
Now, when you're not building apps for friends and family, you should be working on your own side projects.
27
And in doing that, you'll likely use the cloud like AWS.
28
One of the worst messages you can receive is a cloud billing alert like, Hey, it's AWS.
29
Your $25 budget has been exceeded by $2.3 million.
30
Maybe you clicked the wrong button or accidentally created an infinite loop, but the important thing here is not to panic.
31
The easiest solution is to just stop using AWS and pretend nothing ever happened.
32
If Jeff ever sends his guys after you, just tell them your account got hacked.
33
That may or may not work, and
34
if it doesn't, you can at least find comfort in knowing there are many
35
other homeless people out there who simply forgot to turn off an EC2 instance.
36
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.
37
You just made the simple mistake of dropping prod instead of dev.
38
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.
39
If not, now would be a good time to start looking for a new job.
40
Dropping a database is incredibly easy and can be accomplished with a single line of code.
41
You can use this knowledge to fight back against the system, as this person did here, by weaponizing SQL injection against speed cameras.
42
Dropping a database is bad, but at least it's over quickly.
43
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.
44
Sadly, the previous developer died of old age, and was the only one who had any idea how anything in this codebase worked.
45
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.
46
Fuck my life.
47
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,
48
because by that time it'll be time to migrate your legacy codebase into the hot new JavaScript framework of 2025.
49
Speaking of which, something a web developer never wants to hear is that a new, better JavaScript framework has been invented.
50
When you learn a JavaScript framework, you join a tribe, and that means everything outside that tribe is dangerous and terrible.
51
Now normally, you can create an echo chamber to convince yourself
52
that your chosen framework is absolutely 100% the best in every use case.
53
However, at some point, you may be convinced that a better framework does in fact exist.
54
When that day comes, you'll need to turn your back on your tribe and lose many friends in the process.
55
And it's not exactly easy to make new friends when you're a software engineer.
56
I can't sit here.
57
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.
58
Like, let's just move this nav bar from the top over to the side here.
59
It should be an easy change for you to make.
60
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.
61
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.
62
Let's go ahead and change it back.
63
It's no secret that the most important skill of a software engineer is being able to Google things effectively.
64
That means one of the worst things
65
that can happen to you is running into a problem that nobody else has already solved for you.
66
It's painful enough when zero results come back on Google with your error message, but an even worse thing can happen.
67
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.
68
As you scroll down, hoping for a well-documented and detailed solution, you find that all he posted was fixed, all good now.
69
And now you have to figure out the problem all by yourself.
70
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.
71
Thanks for watching, and I will see you in the next one.

הורד אפליקציה

כל מה שאתה צריך כדי לדבר בשטף

הגיית AIציון לכל משפט
תרגול IPAשלוט בכל צליל
אוצר מיליםבנה את מאגר המילים שלך
משחק אוצר מיליםלמד תוך כדי משחק

אותו ערוץ

FOR YOU

המלץ על סרטון

Vocabulary and speaking notes for this lesson

This video has 71 sentences and 1208 words to shadow. The speech runs for 5:14. The speaker talks fast, about 231 words per minute, so expect linked and reduced sounds. 83% of the words are among the 3,000 most common in English; the rest is worth studying before you start.

Key vocabulary in this video

15 words from the video worth learning, with pronunciation and meaning:

WordPronunciationMeaning
developer noun/dɪˈvɛləpɚ/A person or entity engaged in the creation or improvement of certain classes of products.
framework noun/ˈfɹeɪm.wɜːk/A support structure comprising joined parts or conglomerated particles and intervening open spaces of similar or larger size.
database noun/ˈ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.
cloud noun/ˈklaʊ̯d/A visible mass of water droplets suspended in the air.
skill noun/skɪl/A capacity to do something well; a technique, an ability, usually acquired or learned, as opposed to abilities that are regarded as innate.
solve verb/sɒlv/To find an answer or solution to a problem or question; to work out.
legacy noun/ˈlɛɡəsi/Money or property bequeathed to someone in a will.
painful adjective/ˈpeɪn.fl̩/Causing pain or distress, either physical or mental.
convince verb/kənˈvɪns/To make someone believe, or feel sure about something, especially by using logic, argument or evidence.
accidentally adverb/ˌæk.sɪˈdɛnt(ə)li/In an accidental manner; by chance, unexpectedly.
chamber noun/ˈt͡ʃeɪ̯mbɚ/The private room of an individual, especially of someone wealthy or noble.
suffer verb/ˈsʌfɚ/To undergo hardship.
uncle noun/ˈʌŋ.kl̩/The brother or brother-in-law of one’s parent.
suck verb/sʌk/To use the mouth and lips to pull in (a liquid, especially milk from the breast).
comfort noun/ˈkʌm.fət/Contentment, ease.

Phrasal verbs you will hear

WordPronunciationMeaning
figure out verbTo come to understand; to discover or find a solution; to deduce.
go ahead verb/ˌɡoʊ əˈhɛd/To proceed with; to begin.
come back verbTo return to a place.
find out verbTo discover, as by asking or investigating.
go away verbTo depart or leave a place.
go back to verbTo stem from; to originate in.
go through verbTo travel from one end of something to the other.
stand up verbTo rise from a lying or sitting position.

דקדוק בסרטון הזה

המבנים שהדובר משתמש בהם הכי הרבה, עם המילים המדויקות מהסרטון:

מבנהבסרטון
משפטי תנאי (Conditional sentences) if + clause, will/would + verb — תנאי ותוצאה שלוIf not, now would be
סביל (Passive voice) be + past participle — הדגש הוא על מה שקורה, לא על מי שעושה את הפעולהwas told · has been exceeded · has been dropped
הווה מושלם (Present perfect) have/has + past participle — פעולה שקרתה בעבר ועדיין יש לה חשיבות או השפעה עכשיוhaven't figured · has been exceeded · has been dropped
משפטי זיקה (Relative clauses) who / which + clause — מידע נוסף על אדם או דברcompany, which will · guy who got · one who had

Pronunciation to watch

The speaker uses 19 contractions and reduced forms, such as you'll, you're, doesn't. Say them the short way, as you hear them.

  • The “sh” and “zh” sounds: 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/
  • Long words — get the stress right: 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̩/

How to practise with this video

  1. Listen to the whole video once without speaking and note the words you do not know.
  2. Start at 0.75× speed, shadow it sentence by sentence, then go back to normal speed once it feels easy.
  3. Record yourself and compare with the original, paying attention to words like developer, framework, database.

מהי טכניקת השאדואינג?

שאדואינג היא טכניקת למידת שפה מבוססת מדע שפותחה במקור להכשרת מתורגמנים מקצועיים ופופולרית על ידי הפוליגלוט ד"ר אלכסנדר ארגואלס. השיטה פשוטה אך עוצמתית: אתה מקשיב לאודיו באנגלית ילידית וחוזר עליו בקול רם מיד — כמו צל העוקב אחרי הדובר עם עיכוב של 1–2 שניות בלבד. בניגוד להאזנה פסיבית או תרגילי דקדוק, שאדואינג מכריח את המוח והשרירים בפה לעבד ולשחזר דפוסי דיבור אמיתיים בו זמנית. מחקרים מראים שזה משפר משמעותית את דיוק ההגייה, האינטונציה, הקצב, הדיבור המחובר, הבנת השמיעה ושטף הדיבור — מה שהופך אותו לאחת השיטות היעילות ביותר להכנה לIELTS Speaking ולתקשורת באנגלית בעולם האמיתי.

טכניקת Shadowing: קרא את המדריך המלא שלב אחר שלב →