Shadowing Practice: The Art Of Winning In Tech - Learn English Speaking with Video

Kies een oefenmodus

Elke modus opent een volledig scherm oefenruimte.

89 zinnen
Als zinnen te kort of te lang zijn, klik op Bewerken om ze aan te passen.
1
There has never been a better time to be a software engineer.
2
I know everyone's scared about the whole AI wave, but if you're anything like me, you got interested in software because of the ability to make something real.
3
Something another person could actually use.
4
Something that could blow up and change the world, all while just needing a laptop and an idea.
5
And that has never been more achievable than now.
6
What used to take a team of five can now take one person.
7
What used to take years of learning syntax and documentation and writing every single line by hand, you can now do in a fraction of the time.
8
And trust me, I know everywhere you look and all over the comments of this video, people are gonna say software developers will be completely wiped out.
9
But the ones getting wiped out by the AI wave aren't losing because they're bad developers, they're losing because that world of software is fading out.
10
But the people winning, you know that one guy in your classes with five internships and a job lined up?
11
Or the guy who built something real enough that a company just hired them for it?
12
Or the back-end engineer at a normal tech company who became
13
so productive with AI that they now own systems they would have never touched?
14
Or the random developer charging $50 a month for a tool they built in a weekend?
15
or the founders chasing a vision that they actually believe in with a team of two instead of twenty, they're all winning for the same reason.
16
They understood the new rules faster, about what to build, how to build it, and how to use every resource available to close the gap between where they are and where they want to be.
17
So instead of getting wiped out by this new wave of software engineering...
18
Picture two types of people.
19
The first person is the spectator.
20
For whatever reason, they never fully leaned into the AI wave, and honestly, part of it's probably because the entire space feels overwhelming.
21
They hear LLMs, RAG, Agents, GBT, Claude, OpenAI, Anthropic, and after a certain point, it just all starts blending into one giant cloud of AI words.
22
Or they've been told that using AI somehow makes them a worse programmer, so they keep their distance from it.
23
But on the other hand, you have the surfer.
24
The surfer understands that this is a field built on abstraction.
25
Nobody calls you a fake programmer for using frameworks or libraries, stack overflow, random open source code where you don't even know how it works.
26
So instead of resisting the wave, they learn how to move with it.
27
They use AI to learn fundamentals faster, to experiment faster, to close the gap between what they can imagine and what they can actually build.
28
Maybe you're building web apps and you use AI to scaffold an entire dashboard in a day.
29
Or maybe you're building a game engine
30
and using AI to help explain some brutal graphics concept that would have taken you hours to decode from documentation alone.
31
The leverage looks different depending on the field, but the surfers, regardless, are experimenting.
32
They're shortening the distance between idea and execution.
33
They have an idea and immediately test it.
34
They automate boring parts of their workflow.
35
They use AI to understand unfamiliar code bases faster.
36
To research faster.
37
To prototype faster.
38
To debug faster.
39
To learn faster.
40
Their feedback loops are insanely short.
41
And that matters because software engineering is becoming more and more of a creativity game.
42
In the sense that the people that are winning are the people noticing things.
43
Connecting things.
44
Building weird tools that nobody even thought of before.
45
And following curiosity fast enough before the excitement disappears.
46
Because a few years ago, if you wanted to test an ambitious idea, the barrier was enormous.
47
Now some random student can lock in for a weekend and accidentally build something that thousands of people use.
48
And I think a lot of developers still haven't adjusted to how insane this shift actually is.
49
They're still waiting until they know enough or until they master
50
that one language or framework or just completely distancing themselves from this new wave of technology.
51
Meanwhile, the surfers moving the fastest are already in the water, building, testing, learning, shipping, adjusting,
52
because programming is becoming less about manually typing every brick yourself and more about what should exist in the first place.
53
The bottleneck is no longer can you write the code, it's can you think clearly, can you recognize good ideas, can you move on them quickly, can you learn fast enough to keep up with your own ambition.
54
Because AI doesn't remove the need for builders, if anything it raises the ceiling for the ones that actually build.
55
But adapting to this new wave isn't just about using AI, it's about learning how to think clearly while using it.
56
Which is why you need to- You can't just build in silence anymore.
57
The people getting opportunities right now, like internships, referrals, startup roles, even research positions, are often the ones who are most visible.
58
They're building their projects and they're also posting it on LinkedIn.
59
Or they're doing short demo videos on Twitter.
60
Or maybe they're just writing about random things that they learned from a class, or a bug, or a failed project, or a random opinion that they have about programming.
61
Not because they're influencers, but it signals that this person is actively building.
62
And in this new era of software engineering, especially at companies that are literally shaping this wave like OpenAI or Anthropic,
63
the people who are reviewing talent here are looking for builders who are already in motion, not just people who say that they're interested.
64
So you don't need a perfect portfolio, you just need a visible one.
65
And the third part of this is that you have to stop over-filtering what you're allowed to build.
66
People get stuck because they keep asking, is this idea even good enough for my resume or for my portfolio?
67
Or they might ask, am I skilled enough or should I wait until I know more?
68
But the people who are actually improving are just using everything available to them and just building it anyway.
69
So using AI, libraries, templates, random GitHub repos, documentation, they're trying to brute force learning through building.
70
Even if it feels not good enough or maybe it feels too good
71
and it feels ambitious or if it feels messy or something that one person shouldn't be able to build.
72
That's exactly the point.
73
Because the fastest way to become that kind of programmer, the one who just builds things and makes it work, is to stop negotiating with yourself every time that you get an idea.
74
You build it, ship it, show it, iterate, and slowly your identity starts to catch up with your behavior.
75
And the one thing under all of that, the thing that lets you keep up with your own ambition is to never stop learning, which is why I genuinely got excited when I saw that Brilliant Today sponsor just dropped something game-changing.
76
This is the new Brilliant.
77
It's a personal tutor for math and coding, and it's the fastest tool I've used to actually get good at this stuff.
78
It sits on your screen with you, adapts to how you think, and makes hard concepts feel like puzzles that you actually want to solve.
79
The curriculum covers everything from the fundamentals all the way through college level and above in subjects like math and coding, built by people from MIT,
80
Harvard, and Stanford, so you know you're getting the best of the best.
81
And for where we're at in software right now, the coding side is specifically focused on the things that actually matter, such as logical reasoning, debugging instincts, thinking clearly under complexity.
82
It's also there every day.
83
No scheduling, no friction, you can just open it and go.
84
So if you want to level up as a developer and try Brilliant, click the link below or scan the QR code to get started with Brilliant's tutor for free.
85
You can upgrade to Premium to unlock all courses
86
and right now lattice viewers can save 20 off an annual subscription at brilliant.org slash lattice
87
so thank you once again to brilliant for sponsoring this video
88
and thank you to everyone for watching i'm really trying to up the levels like editing better uploading more
89
and all that stuff so subscribe like comment share everything thank you

App downloaden

Alles wat je nodig hebt om vloeiend te spreken

AI UitspraakScoor elke zin
IPA OefeningBeheers elk geluid
WoordenschatBouw je woordenschat op
WoordenspelLeren terwijl je speelt
FOR YOU

Aanbevolen Video

Woordenschat en spreektips bij deze les

Deze spreekles op niveau B2 is gebaseerd op de video “The Art Of Winning In Tech”. Deze woorden komen het vaakst terug: build, wave, faster, software, random. Deze video bevat 89 zinnen en 1446 woorden om na te spreken. Het gesproken deel duurt 6:24. De spreker praat snel, ongeveer 226 woorden per minuut, dus reken op verbonden en ingeslikte klanken. 83% van de woorden hoort bij de 3.000 meest gebruikte Engelse woorden; de rest kun je beter vooraf bekijken.

Belangrijke woorden in deze video

De 15 moeilijkste woorden uit de video, met uitspraak en betekenis:

WoordUitspraakBetekenis
developer zelfstandig naamwoord/dɪˈvɛləpɚ/ontwikkelaar, ontwerper
surfer zelfstandig naamwoord/ˈsɜː(ɹ)fə(ɹ)/surfer, internetter
programmer zelfstandig naamwoord/ˈpɹoʊɡɹæmɚ/programmeur
wipe werkwoord/waɪp/vegen, smeren
debug werkwoord/diːˈbʌɡ/debuggen
lattice zelfstandig naamwoord/ˈlæt.ɪs/raster, latwerk
internship zelfstandig naamwoord/ˈɪntɜːnʃɪp/stage
tutor zelfstandig naamwoord/ˈtjuːtəː/studiebegeleider, mentor
builder zelfstandig naamwoord/ˈbɪl.dəɹ/bouwer, bouwster
ambition zelfstandig naamwoord/æmˈbɪʃ.ən/eerzucht, ambitie
ambitious bijvoeglijk naamwoord/æmˈbɪʃ.əs/eerzuchtig, ambitieus
adapt werkwoord/əˈdæpt/aanpassen
sponsor zelfstandig naamwoord/ˈspɒn.səː/sponsor
adjust werkwoord/əˈd͡ʒʌst/aanpassen, verstellen
mathematics zelfstandig naamwoord/mæθ(.ə)ˈmæt.ɪks/wiskunde, mathematiek

Grammatica in deze video

De structuren die de spreker het meest gebruikt, met de exacte woorden uit de video:

StructuurIn de video
“Used to” used to + werkwoord — een vroegere gewoonte of toestand die niet meer kloptused to take
Betrekkelijke bijzinnen who / which + zin — extra informatie over een persoon of dingguy who built · ones who are · people who are
Present perfect have/has + voltooid deelwoord — iets uit het verleden dat nu nog telthas never been · they've been told · haven't adjusted

Uitspraak om op te letten

De spreker gebruikt 30 samentrekkingen en verkorte vormen, zoals they're, you're, don't. Spreek ze kort uit, zoals je ze hoort.

  • De klanken “sh” en “zh”: documentation /ˌdɑkjəmɛnˈteɪʃən/, internship /ˈɪntɜːnʃɪp/, ambition /æmˈbɪʃ.ən/, ambitious /æmˈbɪʃ.əs/, abstraction /æbˈstɹæk.ʃn̩/
  • Lange woorden — let op de klemtoon: developer /dɪˈvɛləpɚ/, documentation /ˌdɑkjəmɛnˈteɪʃən/, portfolio /pɔːtˈfəʊ.liˌəʊ/, mathematics /mæθ(.ə)ˈmæt.ɪks/, achievable /əˈt͡ʃivəbəl/

Klanken die Nederlandstaligen lastig vinden:

  • Stemhebbende eindmedeklinker — /b/, /d/, /g/, /z/, /v/ niet verscherpen: debug /diːˈbʌɡ/, dashboard /ˈdæʃˌboɹd/, decode /dɪˈkəʊd/, scaffold /ˈskæf.əld/, fade /feɪd/
  • /æ/ — opener dan de Nederlandse “e”: programmer /ˈpɹoʊɡɹæmɚ/, lattice /ˈlæt.ɪs/, ambition /æmˈbɪʃ.ən/, ambitious /æmˈbɪʃ.əs/, adapt /əˈdæpt/
  • /g/ — een harde plofklank, geen Nederlandse “g”: programmer /ˈpɹoʊɡɹæmɚ/, debug /diːˈbʌɡ/, negotiate /nəˈɡəʊ.ʃi.eɪt/, graphics /ˈɡɹæfɪks/

Zo oefen je met deze video

  1. Luister de hele video één keer zonder te spreken en noteer de woorden die je niet kent.
  2. Begin op 0,75× snelheid, spreek zin voor zin na en ga terug naar normale snelheid zodra het makkelijk gaat.
  3. Neem jezelf op en vergelijk met het origineel; let daarbij op woorden als developer, surfer, programmer.

Wat is de Shadowing-techniek?

Shadowing is een wetenschappelijk onderbouwde taalleermethode die oorspronkelijk is ontwikkeld voor professionele tolkentraining en gepopulariseerd door polyglot Dr. Alexander Arguelles. De methode is eenvoudig maar krachtig: je luistert naar native Engelse audio en herhaalt het onmiddellijk hardop — als een schaduw die de spreker volgt met slechts 1–2 seconden vertraging. In tegenstelling tot passief luisteren of grammaticadrills, dwingt shadowing je hersenen en mondspieren om echte spraakpatronen tegelijkertijd te verwerken en te reproduceren. Onderzoek toont aan dat het de uitspraaknauwkeurigheid, intonatie, ritme, verbonden spraak, luisterbegrip en spreekvaardigheid aanzienlijk verbetert — waardoor het een van de meest effectieve methoden is voor IELTS Speaking-voorbereiding en echte Engelse communicatie.

Shadowing-techniek: lees de volledige stap-voor-stap-gids →