Shadowing Practice: 7 Things No Programmer Ever Wants to Hear - Learn English Speaking with Video
Creando lección...
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.
📺 Mismo canal
B21
10 very promising Open Source Projects you haven’t heard of
American AccentBusiness EnglishUniversity StudentsWorking Adults
B21
7 Programming myths that waste your time
American AccentBusiness EnglishUniversity StudentsWorking Adults
C11
DHH has gone completely off the rails...
American AccentBusiness EnglishUniversity StudentsWorking Adults
C12
DNS Explained in 100 Seconds
American AccentBusiness EnglishUniversity StudentsWorking Adults
B23
Anthropic begged the world to stop AI… then shipped this
American AccentBusiness EnglishUniversity StudentsWorking Adults
B22
One man just liberated Fable... and now it’s illegal
American AccentBusiness EnglishUniversity StudentsWorking Adults
B21
80% of programmers are NOT happy… why?
American AccentBusiness EnglishUniversity StudentsWorking Adults
B24
Raspberry Pi Explained in 100 Seconds
American AccentBusiness EnglishUniversity StudentsWorking Adults
C12
Did Google just kickstart the intelligence explosion?
American AccentBusiness EnglishDaily ConversationUniversity Students
C13
Tragic mistake... Anthropic leaks Claude’s source code
American AccentBusiness EnglishUniversity StudentsWorking Adults
C1100+ Docker Concepts you Need to Know
American AccentBusiness EnglishUniversity StudentsWorking Adults
C17
When open-sourcing your code goes wrong...
American AccentBusiness EnglishUniversity StudentsWorking Adults
C129
Docker in 100 Seconds
American AccentBusiness EnglishUniversity StudentsWorking Adults
C13
The mystery is solved... and the answer is 40x cheaper than Claude
American AccentBusiness EnglishUniversity StudentsWorking Adults
B28
An ex-OpenAI researcher just deleted language from the LLM...
American AccentBusiness EnglishUniversity StudentsWorking Adults
B29
25 crazy software bugs explained
American AccentBusiness EnglishUniversity StudentsWorking Adults
B29
Git Explained in 100 Seconds
American AccentBusiness EnglishUniversity StudentsWorking Adults
B25
There's a new Linux distro in town for developers...
American AccentBusiness EnglishUniversity StudentsWorking Adults
B25
The "vibe coding" mind virus explained…
American AccentBusiness EnglishUniversity StudentsWorking Adults
B24
Linux got wrecked by backdoor attack
American AccentBusiness EnglishUniversity StudentsWorking Adults
✨ Recomendar Video
B22
751 oraciones
7 Conversations Every Ambitious Person Needs to Hear | Dear Leila
American AccentBusiness EnglishDaily ConversationUniversity Students
B210
175 oraciones
I Gave the MIT Commencement Speech
American AccentBusiness EnglishDaily ConversationUniversity Students
B21
583 oraciones
Episode 531: Shallow feedback and my coworker is a huge sloperator
Business EnglishUniversity StudentsWorking Adults
B21
202 oraciones
SOFTWARE ENGINEER Interview Questions & TOP SCORING ANSWERS!
Business EnglishInterview EnglishUniversity Students
B21
125 oraciones
Practical Advice for Creative Projects - Extra Credits Gaming
Business EnglishUniversity StudentsWorking Adults
B21
169 oraciones
Can This Vibe Coder Beat a Senior Developer?
Business EnglishUniversity StudentsWorking Adults
B21
208 oraciones
Graphic Designers Were Trained to Be Replaceable
Business EnglishUniversity StudentsWorking Adults
C11
21 oraciones
Business is Hard Until You Design it Like This
American AccentBusiness EnglishWorking Adults
B22
278 oraciones
AI Food Slop is Here
Business EnglishUniversity StudentsWorking Adults
B23
63 oraciones
How To Land Your First Junior Dev Role
Business EnglishInterview EnglishUniversity Students
Vocabulario y notas de pronunciación para esta lección
Este vídeo tiene 71 frases y 1208 palabras para practicar shadowing. La parte hablada dura 5:14. El hablante habla rápido, unas 231 palabras por minuto, así que espera sonidos enlazados y reducidos. El 83 % de las palabras está entre las 3.000 más comunes del inglés; conviene repasar el resto antes de empezar.
Vocabulario clave de este vídeo
15 palabras del vídeo que vale la pena aprender, con su pronunciación y significado:
| Palabra | Pronunciación | Significado |
|---|---|---|
| developer sustantivo | /dɪˈvɛləpɚ/ | desarrollador |
| framework sustantivo | /ˈfɹeɪm.wɜːk/ | entramado, armazón |
| database sustantivo | /ˈdeɪtəˌbeɪs/ | base de datos, banco de datos |
| cloud sustantivo | /ˈklaʊ̯d/ | nube, nimbo |
| skill sustantivo | /skɪl/ | destreza, habilidad |
| solve verbo | /sɒlv/ | resolver, solucionar |
| legacy sustantivo | /ˈlɛɡəsi/ | legado |
| painful adjetivo | /ˈpeɪn.fl̩/ | doloroso |
| convince verbo | /kənˈvɪns/ | convencer, llevar al huerto |
| accidentally adverbio | /ˌæk.sɪˈdɛnt(ə)li/ | accidentalmente, sin querer |
| chamber sustantivo | /ˈt͡ʃeɪ̯mbɚ/ | cámara, alcoba |
| suffer verbo | /ˈsʌfɚ/ | sufrir, penar |
| uncle sustantivo | /ˈʌŋ.kl̩/ | tío |
| suck verbo | /sʌk/ | chupar, sorber |
| comfort sustantivo | /ˈkʌm.fət/ | comodidad, confort |
Phrasal verbs que vas a escuchar
| Palabra | Pronunciación | Significado |
|---|---|---|
| figure out verbo | averiguar, captar | |
| go ahead verbo | /ˌɡoʊ əˈhɛd/ | venga, adelante |
| find out verbo | averiguar, anoticiarse | |
| go away verbo | irse, marcharse | |
| go through verbo | atravesar | |
| stand up verbo | levantarse, ponerse de pie | |
| turn off verbo | apagar |
Gramática en este vídeo
Las estructuras que más usa el hablante, con las palabras exactas del vídeo:
| Estructura | En el vídeo |
|---|---|
| Oraciones condicionales if + oración, will/would + verbo — una condición y su resultado | If not, now would be |
| Voz pasiva be + participio pasado — importa lo que ocurre, no quién lo hace | was told · should be prepared · has been exceeded |
| Present perfect have/has + participio pasado — una acción pasada que sigue importando ahora | haven't figured · has been exceeded · has been dropped |
| Oraciones de relativo who / which + oración — información extra sobre una persona o cosa | company, which will · guy who got · one who had |
Pronunciación a tener en cuenta
El hablante usa 19 contracciones y formas reducidas, como you'll, you're, doesn't. Dilas en su forma corta, tal como las oyes.
- Los sonidos de “sh” y “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/
- Palabras largas — cuida el acento: 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̩/
Cómo practicar con este vídeo
- Escucha el vídeo entero una vez sin hablar y anota las palabras que no conoces.
- Empieza a velocidad 0,75×, haz shadowing frase por frase y vuelve a la velocidad normal cuando te resulte fácil.
- Grábate y compara con el original, prestando atención a palabras como developer, framework, database.
¿Qué es la Técnica de Shadowing?
Shadowing es una técnica de aprendizaje de idiomas respaldada por la ciencia, desarrollada originalmente para la formación de intérpretes profesionales y popularizada por el políglota Dr. Alexander Arguelles. El método es simple pero poderoso: escuchas audio en inglés nativo y lo repites en voz alta de inmediato, como una sombra que sigue al hablante con solo 1-2 segundos de retraso. A diferencia de la escucha pasiva o los ejercicios de gramática, el shadowing obliga a tu cerebro y músculos de la boca a procesar y reproducir simultáneamente patrones de habla reales. Las investigaciones muestran que mejora significativamente la precisión de la pronunciación, la entonación, el ritmo, el habla conectada, la comprensión auditiva y la fluidez al hablar, convirtiéndola en una de las metodologías más efectivas para la preparación del IELTS Speaking y la comunicación en inglés en el mundo real.