Shadowing-Übung: 12 Important Concepts In the Age of AI Software Development - Englisch Sprechen Lernen mit Video
Übungsmodus wählen
Jeder Modus öffnet einen Übungsraum im Vollbild.
164 Sätze
Wenn Sätze zu kurz oder zu lang sind, klicke auf Edit, um sie anzupassen.
1
Hey guys, so obviously things are changing.
2
They have changed a lot over the past couple years, especially the past year, and it's only speeding up.
3
And we've gone from kind of a standard workflow of writing
4
code to using different AI tools with more attention on things like planning, reading, reviewing, and testing code.
5
Now with that said, just because you won't be writing as much code anymore, or maybe not even writing any code,
6
it doesn't mean that you shouldn't understand what's going on and what the AI is generating.
7
I think being able to read code is now one of the most important skills.
8
So I think the focus is shifting a bit.
9
Fundamentals like functions, loops, conditionals, data types, that's all still a must.
10
You have to learn those.
11
Without those, you're pretty much going to be lost.
12
But it's less important to memorize every function or method in a language or a library or framework.
13
Most developers were looking that stuff up before anyway.
14
I think what really matters now is why it belongs there, the data that it's working with,
15
and just how it fits into the rest of the project.
16
So in this video, I want to go over the concepts
17
that I think are most important to understand if you're going to be using AI as a developer.
18
And this is not a full lesson on each one.
19
It's more of a checklist of things to pay attention to when AI gives you code.
20
So let's get into it.
21
So before we dive in, this video is sponsored by CodeRabbit.
22
You know that feeling when a PR comes in and there's 47 files changed, GitHub just throws them at you alphabetically.
23
There's no sense of what depends on what, there's no logical order.
24
And now that AI is writing more of our code, these PRs are only getting bigger.
25
So CodeRabbit review was built specifically for this.
26
It reorganizes the diff into groups of related changes with ordered layers
27
so that Foundational stuff like data models come before the code
28
that depends on them and every layer has an AI summary
29
and inline diagrams You can also drop inline comments You can navigate with keyboard shortcuts
30
and you can submit your github review without ever leaving the tab It's also opt -in per reviewer
31
so your teammates who prefer the default github experience can just ignore it entirely
32
And it's free to try right now during early access comment.
33
You can read more about it in the link in the description below.
34
All right, guys, so we're going to cover a bunch of very important concepts, and I'm not going to just define what that concept is, but I'm going to relate it to agentic coding.
35
And of course, these are important regardless, even, you know, long before AI, but I'm going to, like I said, relate them to coding with AI.
36
Now, the first three are very closely related, and they're about the flow of your program.
37
So number one is control flow.
38
And this is the order that your code runs in.
39
So what happens first, what happens next, what happens if something is true, and so on.
40
And this includes things like if statements, loops, try catch blocks.
41
And this matters because AI can generate code that looks clean, but the path through that code could do things like return too early,
42
or maybe it skips validation, or maybe the error handling is in the wrong place.
43
So if you can't follow the flow, then you can't really debug the program.
44
Now, number two, as I said, is related to number one, it's data flow.
45
So data flow is how much, sorry, not how much, but how data moves through your application, and where does it come from, where does it end up,
46
and what changes along the way.
47
So for instance, a very common data flow pattern that we see in is where it starts from a user, right?
48
Usually within a form, within a web page, it gets sent to an API, it gets stored in the database, comes back as JSON, and then it shows up in the UI.
49
Now, this matters because AI might generate multiple files for one feature.
50
And if you can trace the data from that initial user action to the database and back to the screen,
51
that whole feature starts And this is what happens when something goes wrong.
52
So a request fails, a value is missing, a user enters bad data, a database query throws an error.
53
There's a lot of different things obviously that can cause errors and a lot of beginners
54
they only think about the happy path, right?
55
But real software has, it has to handle failure.
56
And AI can generate code that works when everything's perfect, but it all falls apart when something unexpected happens.
57
And I see this over and over again.
58
So you really need to ask, where can this fail?
59
And what happens if it does?
60
And does the user or the developer get a useful message to work with?
61
All right.
62
So you got control flow, data flow, and error flow, So the next one is scope.
63
And scope is where things like variables and functions and other values, it's where they're available in your code.
64
So if a variable is created inside of a specific function, can you use it outside of that function?
65
And the answer is usually no. That's scope.
66
And this matters because AI might create a variable in one place and try to use it somewhere else.
67
Or you might move code around and suddenly something breaks because that variable doesn't exist in that part of the program.
68
this value created where can it be accessed and who's allowed to change it Number five is input and output.
69
I would say most useful pieces of code, they usually take something in and give something back.
70
So if you think about a function, for example, it might take in a user ID and it might return the entire user.
71
An API endpoint might take form data and return a success message.
72
A component might take props and render something on the screen.
73
you can check if the function expects the right arguments, if it returns the right data, and if it fits in with the rest of the app.
74
Number six is state.
75
So state is data that changes over time.
76
And this could be something like a logged in user, a shopping cart, a form input, a loading status, or just data stored in a database.
77
And a lot of bugs happen when the program thinks that the state is one thing, but it's actually something else.
78
So AI might put state in the wrong place, it might it.
79
It might update one thing but forget to update something else.
80
So you want to pay attention to where state lives, who can change it, and what should happen when it changes.
81
Now the next three concepts are closely related to each other
82
and probably the most important in my opinion
83
because they all relate to just how files are created and put together in an efficient way.
84
So number seven, the first one of these three is abstraction.
85
So abstraction is hiding complexity behind something simpler to use.
86
So for example, a function called create user, it might validate input, it might hash a password, save a record to the database, and return the new user.
87
But from the outside, you just see a function called create user.
88
So AI will create abstractions constantly, helpers, services, hooks, middleware, utilities, all that.
89
And good abstraction makes code easier to use and files just to figure out what's happening.
90
So there is a fine line between, you know, too little abstraction and too much.
91
Now, modularity number eight is closely related to abstraction.
92
So once you start hiding logic behind functions and components and services,
93
the next question is where those pieces should live and what each one should be responsible for.
94
So instead of having Routes, controllers, models, components, utilities.
95
I could go on and on.
96
Config files.
97
The idea is simple, though.
98
It's each piece should have a job, right?
99
So you have routes.
100
They handle requests.
101
Controllers or handlers, they decide what happens.
102
Models deal with data.
103
Components deal with UI.
104
Utilities, they handle reusable helper logic.
105
So good modularity makes the code base much easier to navigate,
106
much easier to read, much easier to have multiple team members work on it and so on.
107
Now, number nine, architecture is the overall structure of the application.
108
So where does the front end live?
109
Where does the back end live?
110
The database?
111
How do they communicate?
112
What files are responsible for what?
113
And you don't need to be a software architect, but you should understand the basic shape of what you're building.
114
And this matters because with AI, you need to know where to point it.
115
You know, if you want to add an endpoint, where should that go?
116
If you want to change how data is displayed, is that the front end, is that the back end, or is it both?
117
You don't need every detail memorized, but you should understand the map.
118
So just to kind of recap those three concepts, you have abstraction, which is mostly about simplifying pieces of logic,
119
modularity, which is about organizing those pieces, as a whole and how everything fits together.
120
Now, the reason that this stuff is more important than ever, at least in my opinion, is because AI can generate a lot of code very quickly,
121
but it doesn't always understand the long -term shape of your project, no matter how much context you give it.
122
It might solve the immediate problem, but put the logic in the wrong place or create an unnecessary abstraction, duplicate something that already exists.
123
And that's the difference between agentic coding and vibe coding.
124
is basically saying build this feature and you just accept whatever comes back
125
and just hope it works and doesn't wreck something else.
126
Where a more serious AI workflow is being able to say, you know, this logic belongs in a service, not in a component, or this helper is unnecessary.
127
That's why when I use AI, I use very specific workflows along with skills and agents, sub -agents that let me make all those decisions.
128
I'm going to be using in my next video to really show you what, what I think a good AI workflow looks like.
129
So next we have side effects and side effects are when code changes something outside of itself.
130
So returning a value from a function is one thing, but five other things may happen as a result of that.
131
So things like updating a database, writing to a file, sending an email, modifying state, those can all be side effects.
132
So a function that has no side effects and just simply takes in and give something back, that's called a pure function.
133
And this matters because side effects are where a lot of bugs happen, right?
134
So they make code harder to predict because the function isn't just giving something back, it's changing the world around it in some way.
135
And AI will often mix pure logic and side effects together.
136
So it helps to be able to look at the code and ask, is this just calculating a value or is it changing something somewhere else that I need to know about?
137
Next we have the request response cycle and this one is really geared more toward obviously web development.
138
So in a browser a user will click a button, the browser sends a request, the server receives it, runs some code, maybe talks to a database and then sends a response back.
139
So if you understand that cycle then frameworks like Express,
140
Laravel, Django, Rails or whatever else they start to make a lot more sense and different frameworks have different syntax
141
But a lot of them are solving the same basic problem and doing the same thing, which is receiving a request, doing some work and returning a response.
142
And I would also lump in just like APIs or REST APIs in this as well.
143
So knowing HTTP status codes, knowing the different methods and so on.
144
So next is concurrency.
145
So concurrency is when multiple things are happening during the same period of time.
146
So maybe you have multiple API requests running, users editing data at the same time, background jobs processing, things like that.
147
And this can get tricky because bugs can happen based on timing, right?
148
Something works fine once but breaks when two things happen at nearly the same time.
149
of video conversions, so basically videos to articles, and one job might be processing, another might be waiting, and another might fail,
150
and then another might finish right as the UI is trying to update.
151
So I had a Big issue with that that I worked on for a week straight.
152
So you don't need to be a concurrency expert right away, but you should understand that software doesn't always just run in a perfect neat line.
153
And AI can handle the simple case, but you still need to think about what happens when that timing gets messy.
154
All right.
155
So I know that that was a lot, but the point of this is not to have you master all of this before touching AI.
156
Nobody masters all this overnight.
157
I certainly haven't even come close.
158
The point of this is that there are concepts
159
that you want to keep learning as you build
160
and as you learn because AI can generate code but you still need to understand the shape of what it's generating.
161
And the better you understand these concepts,
162
the better you can just getting AI to write code,
163
but knowing whether that code actually makes sense.
164
All right, so hope you guys enjoyed it, and I will see you next time.
App herunterladen
Alles, was du zum fließenden Sprechen brauchst
KI-AussprachebewertungJeder Satz bewertet
IPA-TrainingJeden Laut meistern
WortschatzBaue deinen Wortschatz auf
VokabelspielSpielend lernen
Gleicher Kanal
FOR YOU
Empfohlenes Video
B24
180 Sätze
Is AI Doom Real... or Just Good Marketing?
Business EnglishUniversity StudentsWorking Adults
B22
25 Sätze
AI's Impact on Education: Pros, Cons, and Coping
Business EnglishUniversity StudentsWorking Adults
![What is AI and ML? [Pt 2] | Generative AI with .NET for Beginners](https://img.youtube.com/vi/Len8KRBFvGo/mqdefault.jpg)
B22
52 Sätze
What is AI and ML? [Pt 2] | Generative AI with .NET for Beginners
Business EnglishUniversity StudentsWorking Adults
C15
104 Sätze
The 7 phases of AI-driven development
British AccentBusiness EnglishUniversity StudentsWorking Adults
C11
315 Sätze
how AI broke the SWE Career Ladder
Business EnglishInterview EnglishUniversity Students
C13
80 Sätze
What is clean code? - Uncle Bob
Business EnglishUniversity StudentsWorking Adults
B23
245 Sätze
How To Become Dangerously Self-Educated (with AI)
Business EnglishUniversity StudentsWorking Adults
![Cloud Providers are changing RAPIDLY [REUPLOAD]](https://img.youtube.com/vi/UVz8_JljpGQ/mqdefault.jpg)
B22
55 Sätze
Cloud Providers are changing RAPIDLY [REUPLOAD]
Business EnglishUniversity StudentsWorking Adults
B23
165 Sätze
How I'd Learn AI From Scratch in 2026 (skip the useless 80%)
American AccentBusiness EnglishUniversity StudentsWorking Adults
B211
89 Sätze
The Art Of Winning In Tech
Business EnglishInterview EnglishUniversity Students
B27
11 Sätze
Cần cập nhật gì về AI - Ali Abdaal #AI #Update #ielts
IELTS PrepBusiness EnglishUniversity Students
B24
261 Sätze
Has AI killed Tailwind?
Business EnglishUniversity StudentsWorking Adults
Wortschatz und Sprechhinweise zu dieser Lektion
Diese Sprechübung auf Niveau B2 basiert auf dem Video „12 Important Concepts In the Age of AI Software Development“. Diese Wörter kommen am häufigsten vor: code, function, happen, user, flow. Dieses Video enthält 164 Sätze und 2352 Wörter zum Nachsprechen. Der gesprochene Teil dauert 14:00. Der Sprecher spricht in natürlichem Tempo, etwa 168 Wörter pro Minute, ähnlich wie im Alltagsgespräch. 84 % der Wörter gehören zu den 3.000 häufigsten im Englischen; den Rest solltest du dir vor dem Üben ansehen.
Wichtiger Wortschatz in diesem Video
Die 15 anspruchsvollsten Wörter aus dem Video, mit Aussprache und Bedeutung:
| Wort | Aussprache | Bedeutung |
|---|---|---|
| abstraction Substantiv | /æbˈstɹæk.ʃn̩/ | Abstraktion |
| workflow Substantiv | /ˈwɝkfloʊ/ | Arbeitsablauf |
| variable Adjektiv | [ˈvæɹ.i.ə.bl̩] | variabel |
| concurrency Substantiv | /kəŋˈkʌɹənsi/ | Gleichzeitigkeit |
| helper Substantiv | /ˈhɛlpɚ/ | Helfer, Helferin |
| modularity Substantiv | Modularität | |
| developer Substantiv | /dɪˈvɛləpɚ/ | Entwickler, Entwicklerin |
| endpoint Substantiv | Endpunkt | |
| memorize Verb | /ˈmɛm.əˌɹaɪ̯z/ | auswendig lernen, memorieren |
| navigate Verb | /ˈnæv.ɪ.ɡeɪt/ | die Richtung vorgeben, steuern |
| controller Substantiv | /kənˈtɹoʊlɚ/ | Regler |
| unnecessary Adjektiv | /ʌnˈnɛs.əˌsɛɹ.i/ | nicht notwendig, unnötig |
| depend Verb | /dɪˈpɛnd/ | abhängen, ankommen |
| alphabetically Adverb | alphabetisch | |
| checklist Substantiv | /ˈt͡ʃɛklɪst/ | Checkliste, Kontrollliste |
Phrasal Verbs, die du hören wirst
| Wort | Aussprache | Bedeutung |
|---|---|---|
| come back Verb | zurückkommen, zurückkehren | |
| end up Verb | sich herausstellen, am Ende irgendwo / etwas sein | |
| fall apart Verb | auseinanderfallen | |
| figure out Verb | herausfinden | |
| speed up Verb | /spiːdˈʌp/ | beschleunigen |
Grammatik in diesem Video
Die Strukturen, die der Sprecher am häufigsten verwendet, mit den genauen Worten aus dem Video:
| Struktur | Im Video |
|---|---|
| Passiv be + Partizip Perfekt – wichtig ist, was geschieht, nicht wer es tut | be lost · is sponsored · was built |
| Present Perfect have/has + Partizip Perfekt – eine vergangene Handlung, die jetzt noch wichtig ist | have changed · we've gone · haven't even come |
| Relativsätze who / which + Satz – eine Zusatzinformation über eine Person oder Sache | abstraction, which is · modularity, which is · thing, which is |
Aussprache, auf die du achten solltest
Der Sprecher verwendet 25 Kurzformen und abgeschwächte Formen, zum Beispiel doesn't, I'm, don't. Sprich sie in der kurzen Form, so wie du sie hörst.
- Die Laute „sh“ und „zh“: abstraction /æbˈstɹæk.ʃn̩/, shortcut /ˈʃɔːtkʌt/, conditional /kənˈdɪʃ.ə.nəl/, hash /ˈhæʃ/, validation /ˌvæl.əˈdeɪ.ʃən/
- Lange Wörter – auf die Betonung achten: concurrency /kəŋˈkʌɹənsi/, developer /dɪˈvɛləpɚ/, unnecessary /ʌnˈnɛs.əˌsɛɹ.i/, conditional /kənˈdɪʃ.ə.nəl/, validation /ˌvæl.əˈdeɪ.ʃən/
Laute, die Deutschsprachigen schwerfallen:
- /w/ — mit runden Lippen, nicht wie das deutsche „w“ (/v/): workflow /ˈwɝkfloʊ/, query /ˈkwɪɹ.i/, password /ˈpæs.wɜɹd/
- Stimmhafter Auslaut — /b/, /d/, /g/, /z/, /v/ am Wortende nicht verhärten: memorize /ˈmɛm.əˌɹaɪ̯z/, depend /dɪˈpɛnd/, config /ˌkənˈfɪɡ/, vibe /vaɪb/, organize /ˈɔɹɡənaɪz/
- /æ/ — offener als „ä“: abstraction /æbˈstɹæk.ʃn̩/, variable [ˈvæɹ.i.ə.bl̩], navigate /ˈnæv.ɪ.ɡeɪt/, validate /ˈvæl.ɪ.deɪt/, handler /ˈhænd.lə/
So übst du mit diesem Video
- Höre dir das ganze Video einmal an, ohne zu sprechen, und notiere die Wörter, die du nicht kennst.
- Beginne mit 0,75-facher Geschwindigkeit, sprich Satz für Satz nach und wechsle zur normalen Geschwindigkeit, sobald es leichtfällt.
- Nimm dich auf und vergleiche mit dem Original; achte dabei auf Wörter wie abstraction, workflow, variable.
Was ist die Shadowing-Technik?
Shadowing ist eine wissenschaftlich fundierte Sprachlerntechnik, die ursprünglich für die professionelle Dolmetscherausbildung entwickelt und durch den Polyglotten Dr. Alexander Arguelles populär gemacht wurde. Die Methode ist einfach aber wirkungsvoll: Du hörst englisches Audio von Muttersprachlern und wiederholst es sofort laut — wie ein Schatten, der dem Sprecher mit nur 1–2 Sekunden Verzögerung folgt. Anders als passives Hören oder Grammatikübungen zwingt Shadowing dein Gehirn und deine Mundmuskulatur, gleichzeitig echte Sprachmuster zu verarbeiten und zu reproduzieren. Studien zeigen, dass es Aussprachegenauigkeit, Intonation, Rhythmus, verbundene Sprache, Hörverständnis und Sprechflüssigkeit signifikant verbessert — was es zu einer der effektivsten Methoden für die IELTS Speaking-Vorbereitung und reale englische Kommunikation macht.