Shadowing Practice: They want mediocre developers... - Learn English Speaking with Video
בחר מצב תרגול
כל מצב פותח חדר תרגול במסך מלא.
133 משפטים
אם המשפטים קצרים או ארוכים מדי, לחץ על ערוך כדי להתאים אותם.
1
I miss the good old days when technical debt
2
and student debt were the only debts we had to worry about in the software world.
3
Looking back at it, technical debt was actually quite fun.
4
We would take shortcuts to move faster,
5
ignore best practices to meet a deadline,
6
or delay updating a library because we were in no mood to work through the side effects.
7
The worst that could've happened was
8
that you would end up paying for it later through increased complexity in systems that nobody wanted to touch.
9
But ultimately, this increased complexity would increase your job security because
10
if If you were the only person who understood a messy part of the system,
11
you would suddenly become very hard to replace.
12
This is why for the past 20 years,
13
software engineering has been a pretty nice gig,
14
with a lot of perks and more than decent paychecks.
15
And I'm not making this video to tell you that all these are going to end,
16
but I want to discuss a new emerging kind of debt which will actually make our lives much more difficult.
17
Adios Money recently posted about a new concept called Comprehension Debt
18
and in this Monday morning review will look at the importance of being able to think
19
and solve problems in the generated code era.
20
Comprehension debt is the growing gap between how much code exists in your system
21
and how much of it anyone on the team can genuinely explain.
22
At first, this doesn't look like a problem,
23
since most AI-generated code looks really clean at first and it might look like all the best practices are being followed.
24
But underneath that, something subtle starts to shift because the understanding of the system begins to slowly degrade.
25
In a recent study, engineers were asked to learn a new library.
26
Some of them used AI to generate solutions,
27
others used it more as a guide to explore concepts and ask questions.
28
Both groups completed the task in roughly the same time,
29
so from a productivity perspective, everything looked identical.
30
But when they were tested afterwards,
31
the group that relied on generation performed significantly worse,
32
especially when it came to debugging.
33
And debugging is where things become very real very quickly.
34
If you've been involved in software for a while,
35
you probably know that reading and understanding code at a deep level is one of the most difficult parts of the job.
36
I'm not talking here about going through some random syntax filled with for loops and if statements.
37
I'm talking about complex implementations,
38
which have interactions, implicit assumptions,
39
and behavior that only makes sense once you follow the entire execution path end-to-end.
40
This part is so difficult that you'll go through code you wrote yourself six months ago
41
and you'd still be confused trying to reconstruct what you were thinking at the time.
42
When everything works, speed feels like the most important metric.
43
The moment something breaks, the only thing that matters is whether someone can explain what the system is doing and why.
44
And, if I have issues understanding my own code from six months ago
45
and I can proudly call myself an average developer with a weird accent and a copied YouTube channel,
46
I expect
47
that most of us will have a lot of issues understanding thousands of lines of code generated in a couple of minutes.
48
For a long time, writing code and reviewing it acted as a natural bottleneck in development.
49
It slowed teams down, but it also forced engineers to read code written by others,
50
to question decisions, and to build a shared understanding of how the system behaved.
51
The process was one of the main ways knowledge spread across a team.
52
With AI-generated code, the volume changes the nature of that interaction.
53
Code is produced faster than it can be meaningfully reviewed,
54
and because it is usually clean and well-structured,
55
it gives off all the signals that historically indicated quality.
56
And the AI labs are telling you to ignore the problem.
57
You spend your tokens generating code,
58
and then they provide you the tools to review that generated code for the convenient price of $15-25 for each review.
59
In other words, the token sellers just want you to buy more tokens,
60
ideally hundreds of thousands of dollars worth of tokens.
61
I keep trying to avoid highlighting the absurdity of some of these CEOs' comments,
62
but they are making it very tough for me to ignore them.
63
screams trying to inflate the bubble more than focusing on quantity over quality.
64
Sure, you could easily spin up Todo apps in an endless loop to burn through $250,000 in tokens.
65
That would be completely pointless and will consume a few more million gallons of water,
66
but at least the billionaire Jensen Huang with his geeky leather
67
jackets will be happy to see his Nvidia stock keep going through the roof.
68
But I digress.
69
Back to the topic of comprehension debt,
70
there's also a more subtle failure mode that starts to show up in AI-heavy workflows.
71
When an implementation changes and the associated tests are updated to match,
72
the conversation quietly shifts.
73
Instead of asking whether the code behaves correctly,
74
you now have to ask whether the behavior itself is correct.
75
The test passing no longer answered the most important question.
76
As we discussed in last Monday's episode,
77
another common reaction is to rely more on specifications.
78
You define the behavior in detail,
79
review the specification carefully, and let AI handle the implementation.
80
On paper, this creates a clean separation between intent and execution.
81
In practice, translating a specification into working software involves a large number of implicit decisions that rarely get captured in full.
82
Data structures, edge cases, error handling,
83
and performance trade-offs all shape the final behavior in ways that are difficult to fully describe up front.
84
This year's DORA report also highlights this new emerging comprehension crisis.
85
In teams where engineering practices are already solid,
86
where workflows are clear, and where people have a strong mental model of the system they are working on,
87
AI tends to make everything move faster in a way that actually compounds quality.
88
Developers spend less time on repetitive tasks,
89
decisions are made with more context,
90
and the system evolves in a relatively controlled way.
91
But in teams where things are already messy,
92
where architecture has grown organically without much discipline,
93
and where understanding is fragmented across individuals,
94
AI scales all of those issues at the same time.
95
The same acceleration that helps good systems becomes a multiplier for bad ones,
96
and the difference between the two becomes much more visible.
97
What's interesting is that the report states
98
that around 90% of developers are already using AI in their work and more than 80% believe it improves their productivity.
99
But at the same time,
100
a significant portion of them openly admit that they do not fully trust the code that AI produces.
101
So you end up in a situation where developers rely on a tool daily,
102
move faster because of it,
103
and still carry a constant layer of uncertainty about what is actually being generated.
104
The DORA data also highlights something that reinforces this dynamic even further.
105
AI adoption correlates with higher throughput,
106
meaning teams are shipping more changes and moving faster through their backlog.
107
At the same time, delivery instability increases,
108
which means those changes introduce more issues into the system.
109
So basically, you move faster,
110
create more issues, you fix those issues faster,
111
and create even more issues.
112
Your KPIs go through the roof,
113
management has nice graphics to look at,
114
clients are happy to see results,
115
and token sellers are making a lot of money.
116
Everybody is happy and Jensen Huang gets richer.
117
If I'm being honest, I spent the past couple of months worrying about the future of software engineering.
118
AI code generation is far from perfect,
119
it has improved a lot in the past couple of months.
120
However, something feels off.
121
The AI labs are pushing these coding agents hard and we have to pay very little to use their models.
122
However, their computing costs are huge and they are very far from running a profitable business.
123
This is clearly the customer acquisition phase,
124
where their pricing is so low you can't ignore them
125
and their agents are slowly becoming an integral part of the software workflow.
126
And I believe that this comprehension debt is exactly what they need to make sure you can't really walk away later.
127
This is not going to happen overnight,
128
but imagine a world 10 years from now where most of the software engineers have lost most of their critical thinking,
129
problem solving and debugging skills because they are used to delegating all of it.
130
At that point, Anthropic could increase the cost of their agents to thousands of dollars per month
131
and there would be little we could do because most of the skills are lost,
132
we have no idea what our code actually does
133
and the jobs pipeline was destroyed when we decided AI can do a better job than juniors.
הורד אפליקציה
כל מה שאתה צריך כדי לדבר בשטף
הגיית AIציון לכל משפט
תרגול IPAשלוט בכל צליל
אוצר מיליםבנה את מאגר המילים שלך
משחק אוצר מיליםלמד תוך כדי משחק
אותו ערוץ
FOR YOU
המלץ על סרטון
C15
317 משפטים
Give Me 18 Minutes and I’ll Make you Dangerously Smart (with AI)
Business EnglishUniversity StudentsWorking Adults
C13
80 משפטים
What is clean code? - Uncle Bob
Business EnglishUniversity StudentsWorking Adults
C18
70 משפטים
When open-sourcing your code goes wrong...
American AccentBusiness EnglishUniversity StudentsWorking Adults
C12
315 משפטים
how AI broke the SWE Career Ladder
Business EnglishInterview EnglishUniversity Students
C12
12 משפטים
A Return to Code
Business EnglishUniversity StudentsWorking Adults
C111
201 משפטים
The AI Bubble Survives on $1.65 Trillion in Hidden Debt
Business EnglishDaily ConversationUniversity Students
B23
194 משפטים
People Are Mad They're Told to Learn
Business EnglishUniversity StudentsWorking Adults
C12
129 משפטים
How to Become a Great Software Developer — Best Advice from Top-Notch Engineers
Business EnglishInterview EnglishUniversity Students
C13
207 משפטים
The Entry-Level Job Crisis
Business EnglishInterview EnglishUniversity Students
C14
261 משפטים
Stanford CS Professor: AI Can Code. That’s Why You Should Learn Programming | Chris Piech
Business EnglishUniversity StudentsWorking Adults
C111
102 משפטים
World Models explained in 10min..
Business EnglishUniversity StudentsWorking Adults
C11
83 משפטים
DHH has gone completely off the rails...
American AccentBusiness EnglishUniversity StudentsWorking Adults
אוצר מילים והערות הגייה לשיעור הזה
שיעור הדיבור הזה ברמה C1 מבוסס על הסרטון “They want mediocre developers..”. המילים שחוזרות הכי הרבה: code, debt, faster, software, issues. בסרטון הזה יש 133 משפטים ו-1521 מילים לתרגול Shadowing. הדיבור נמשך 7:51. הדובר מדבר מהר, כ-194 מילים בדקה, אז צפו לצלילים מחוברים ומקוצרים. 82% מהמילים נמצאות בין 3,000 המילים הנפוצות ביותר באנגלית; כדאי ללמוד את השאר לפני שמתחילים.
אוצר מילים מרכזי בסרטון הזה
15 המילים המתקדמות ביותר בסרטון, עם ההגייה והמשמעות שלהן:
| מילה | הגייה | משמעות |
|---|---|---|
| token שם עצם | /ˈtoʊkən/ | אֲסִימוֹן, זִ׳יטוֹן |
| comprehension שם עצם | /ˌkɑmpɹɪˈhɛnʃn̩/ | הֲבָנָה |
| debug פועל | /diːˈbʌɡ/ | דיבג |
| messy שם תואר | /ˈmɛsi/ | חסר סדר, מבולגן |
| emerge פועל | /ɪˈmɝd͡ʒ/ | צץ, התגלה |
| behave פועל | /bɪˈheɪv/ | הִתְנַהֵג |
| seller שם עצם | /ˈsɛlɚ/ | מוֹכֵר, מוֹכֶרֶת |
| complexity שם עצם | /kəmˈplɛk.sɪ.ti/ | מורכבות |
| multiplier שם עצם | /ˈmʌltɪˌplaɪəɹ/ | כּוֹפֵל |
| syntax שם עצם | /ˈsɪn.tæks/ | תַּחְבִּיר |
| fragment שם עצם | /ˈfɹæɡmənt/ | פָּרוּר, רְסִיס |
| reinforce פועל | /ˌɹiː.ɪnˈfɔːs/ | חִזֵּק |
| delegate שם עצם | /ˈdɛlɪɡət/ | בא־כוח, נָצִיג |
| acceleration שם עצם | /əkˌsɛl.əˈɹeɪ.ʃən/ | האצה |
| billionaire שם עצם | /ˌbɪl.jəˈnɛɚ/ | מיליארדר, מיליארדרית |
דקדוק בסרטון הזה
המבנים שהדובר משתמש בהם הכי הרבה, עם המילים המדויקות מהסרטון:
| מבנה | בסרטון |
|---|---|
| סביל (Passive voice) be + past participle — הדגש הוא על מה שקורה, לא על מי שעושה את הפעולה | being followed · were asked · were tested |
| הווה מושלם (Present perfect) have/has + past participle — פעולה שקרתה בעבר ועדיין יש לה חשיבות או השפעה עכשיו | has been · you've been involved · has grown |
| משפטי זיקה (Relative clauses) who / which + clause — מידע נוסף על אדם או דבר | person who understood · debt which will |
הגייה ששווה לשים לב אליה
הדובר משתמש ב-11 קיצורים וצורות מקוצרות, כמו I'm, can't, could've. אמרו אותם בצורה הקצרה, כפי שאתם שומעים אותם.
- הצלילים של “th”: throughput /ˈθɹuː.pʊt/, underneath /ˌʌndɚˈniθ/
- הצלילים של “sh” ו-“zh”: comprehension /ˌkɑmpɹɪˈhɛnʃn̩/, shortcut /ˈʃɔːtkʌt/, acceleration /əkˌsɛl.əˈɹeɪ.ʃən/, assumption /əˈsʌm(p).ʃ(ə)n/
- מילים ארוכות — שימו לב להטעמה: complexity /kəmˈplɛk.sɪ.ti/, absurdity /æbˈsɝd.ɪ.ti/, organically /ɔːˈɡænɪkli/, repetitive /ɹɪˈpɛtɪtɪv/, instability /ɪnstəˈbɪlɪti/
צלילים שדוברי עברית מתקשים בהם:
- /w/ — שפתיים מעוגלות, לא /v/: workflow /ˈwɝkfloʊ/, quantity /ˈkwɑn(t)ɪti/
- /æ/ — פתוח יותר מה-“אֶ” העברית, לא כמו “a” ב-“cup”: absurdity /æbˈsɝd.ɪ.ti/, backlog /ˈbæk(ˌ)lɔɡ/, organically /ɔːˈɡænɪkli/, syntax /ˈsɪn.tæks/, fragment /ˈfɹæɡmənt/
- /r/ — הלשון לא נוגעת בשום מקום, לא ה-“ר” הגרונית: comprehension /ˌkɑmpɹɪˈhɛnʃn̩/, correlate /ˈkɔɹəleɪt/, degrade /dɪˈɡɹeɪd/, digress /daɪˈɡɹɛs/, multiplier /ˈmʌltɪˌplaɪəɹ/
איך לתרגל עם הסרטון הזה
- הקשיבו לכל הסרטון פעם אחת בלי לדבר, ורשמו את המילים שאתם לא מכירים.
- התחילו במהירות 0.75×, תרגלו Shadowing משפט אחר משפט, וחזרו למהירות רגילה כשזה מרגיש קל.
- הקליטו את עצמכם והשוו למקור, תוך תשומת לב למילים כמו token, comprehension, debug.
מהי טכניקת השאדואינג?
שאדואינג היא טכניקת למידת שפה מבוססת מדע שפותחה במקור להכשרת מתורגמנים מקצועיים ופופולרית על ידי הפוליגלוט ד"ר אלכסנדר ארגואלס. השיטה פשוטה אך עוצמתית: אתה מקשיב לאודיו באנגלית ילידית וחוזר עליו בקול רם מיד — כמו צל העוקב אחרי הדובר עם עיכוב של 1–2 שניות בלבד. בניגוד להאזנה פסיבית או תרגילי דקדוק, שאדואינג מכריח את המוח והשרירים בפה לעבד ולשחזר דפוסי דיבור אמיתיים בו זמנית. מחקרים מראים שזה משפר משמעותית את דיוק ההגייה, האינטונציה, הקצב, הדיבור המחובר, הבנת השמיעה ושטף הדיבור — מה שהופך אותו לאחת השיטות היעילות ביותר להכנה לIELTS Speaking ולתקשורת באנגלית בעולם האמיתי.