Shadowing Practice: When open-sourcing your code goes wrong... - Learn English Speaking with Video

Kies een oefenmodus

Elke modus opent een volledig scherm oefenruimte.

70 zinnen
Als zinnen te kort of te lang zijn, klik op Bewerken om ze aan te passen.
1
The programming world recently witnessed something unprecedented, the fastest rise of an open source project in the history of the universe.
2
A project that went from failed side project to over 200,000 GitHub stars in a matter of weeks.
3
A project that's already been acquired by OpenAI for probably some absurd amount of money.
4
That project, of course, is OpenClaw, a tool that's not much more than a basic JavaScript AI wrapper.
5
But what most people fail to realize is
6
that every piece of software you use today is built on the shoulders of giants.
7
And sadly, many of those giants died in battle a long time ago.
8
Nearly every piece of meaningful software out there is built with the blood, sweat, and tears of highly creative and talented programmers.
9
What's depressing, though, is that almost all of those programmers never got to reap the glory and money from their own creations.
10
In today's video, we're going to look at the stories of five open-source projects that achieved a meteoric rise, then crashed out under the weight of their own success.
11
It is February 26th, 2026, and you're watching The Code Report.
12
Yesterday, I was working on laying out some sick beats with the Arturia Microfreak.
13
But what I failed to realize is
14
that this commercial product is actually based upon the incredible work of the developer behind Mutable Instruments, Emily Gallay.
15
It's an incredible tool that can make sound waves do anything you can imagine.
16
It's coded by hand in C++, but there was always a problem in the background.
17
Burnout.
18
This project was managed by a solo business owner who just wanted something else in life.
19
And when she decided to move on to a new venture, the project simply faded away.
20
But as the old saying goes, it's better to burn out than to fade away.
21
And that's what happened to a popular project called Faker.js, a project that burned out in spectacular fashion.
22
Faker was a JavaScript library with millions of weekly downloads that generated fake data,
23
which was awesome for automated testing and astroturfing millions of fake users for your social media app to raise money from VCs.
24
But one fateful day in 2022, the developer Maroc Squires did something bold.
25
He deleted the source code, replaced it with the text Endgame, and published version 6.6.6 on NPM.
26
And this instabricked thousands of JavaScript apps when they went to update dependencies.
27
The corporations that depended on his work were rightfully pissed, but he was pissed himself for providing free work with no pay, and made this update in protest.
28
Unfortunately though, he was kicked out of his own project and it was taken over by a new developer, and still lives on today.
29
But sometimes, even projects that are well-funded with big teams can still fail, like Parse.
30
Before Supabase won, and even before Firebase won, there was a backend as a service called Parse in 2011 that provided a database and auth for mobile apps.
31
Developers loved it so much that Facebook acquired it for $85 million in 2013, which was considered a lot of money back then.
32
That gave the project access to the most talented developers in the industry, but just a few years later in 2016, it was killed by Facebook and shut down.
33
Any developer using it was forced to migrate to a new platform.
34
Zuck decided that hosting mobile app infrastructure was a waste of time, but this story has a semi-happy ending.
35
The code behind Parse Server was open-sourced, which allowed developers to self-host and maintain it independently.
36
But if you're an elderly developer from that time period, another project you might remember is Meteor, one of the first frameworks to do full-stack JavaScript before it was cool.
37
In 2013, Ruby on Rails was all the rage, but Meteor looked like the next big thing because it did all the same stuff,
38
but relied entirely on JavaScript instead of the beautiful yet esoteric Ruby language.
39
Its design also used WebSocket connections and stateful servers to perform instant UI updates that felt magical on early demos, but that was also part of the problem.
40
When apps went into production, they were difficult to maintain and didn't easily scale horizontally in the cloud.
41
When React and Angular hit the scene a few years later, devs decided it was best to separate the client from the server again, and its popularity slowly faded into the abyss.
42
Ironically, future frameworks like Next would start reintroducing these same concepts once again, but timing is everything in software, and Meteor was just born before its time.
43
Well, actually, maybe timing isn't everything, like in the case of Open Solaris.
44
In 2005, Linux was the dominant open-source operating system on servers,
45
But this superior new horse entered the race based on Sun Microsystems' Solaris Unix.
46
It has the ZFS file system, D-Trace observability, and even had containers before Docker was a thing.
47
On paper, it was the far better OS, but then in 2010, something really bad happened.
48
Oracle acquired Sun Microsystems, and almost overnight, the project's future evaporated.
49
Open development stopped, source releases quietly disappeared, and the community realized the experiment was over.
50
Oracle put Solaris back behind closed doors to protect its enterprise business, forcing developers to fork the last available code.
51
So even though the timing was great and it was technically brilliant, it failed because the ownership changed.
52
But possibly the most spectacular open source failure of all time is one you didn't see coming,
53
Mozilla Firefox, which is a prime example of when open sourcing your code goes wrong.
54
You see, in the 1990s, Netscape dominated the web browser market share, but Microsoft wanted a piece of that pie.
55
So what Microsoft did was bundle Internet Explorer directly into Windows, turning the browser into a free default instead of a product you had to choose.
56
When Netscape started losing market share, their response was radical.
57
Open sourced the browser and rallied the internet to its side.
58
The internet cheered, but the problem is that the code was a mess.
59
Eventually, this code became the Mozilla project, but the transition was a nightmare that required a near-total rewrite of all its legacy code.
60
Meanwhile, Internet Explorer rapidly captured new users through distribution alone.
61
By the time Mozilla eventually produced Firefox, which was faster, safer, and just better, Netscape itself was already dead.
62
The company lost the browser war, proving that open source can build better software, but it can't beat platform control and distribution.
63
Ironically, though, that same failure revived browser competition and laid the groundwork for the modern web, meaning Firefox succeeded technically by first losing commercially.
64
But if you dream of building your own failed open-source project in 2026, you need to know about CodeRabbit, the sponsor of today's video.
65
They just launched a new feature that lets you customize how their AI code reviewer writes pull request summaries.
66
So instead of wasting time decoding your team's PRs, you and your team can tell CodeRabbit exactly what information you want to see in every summary.
67
Like here, we made a doc telling it to include what changed and why, with special callouts to any branching changes or new dependencies.
68
CodeRabbit will follow these instructions to make sure that every PR gets a clean summary that everyone can quickly scan.
69
It's already saving dev teams hundreds of hours, and you can try it for free with the link below.
70
This has been The Code Report, thanks for watching, and I will see you in the next one.

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

Zelfde Kanaal

FOR YOU

Aanbevolen Video

Woordenschat en spreektips bij deze les

Deze video bevat 70 zinnen en 1266 woorden om na te spreken. Het gesproken deel duurt 6:38. De spreker praat snel, ongeveer 191 woorden per minuut, dus reken op verbonden en ingeslikte klanken. Slechts 78% van de woorden hoort bij de 3.000 meest gebruikte Engelse woorden, dus de woordenschat is pittig.

Belangrijke woorden in deze video

15 minder gangbare woorden uit de video, met uitspraak en betekenis:

  • developer /dɪˈvɛləpɚ/ (zelfstandig naamwoord) — ontwikkelaar, ontwerper. A person or entity engaged in the creation or improvement of certain classes of products.
  • server /ˈsɝvɚ/ (zelfstandig naamwoord) — server. A program that provides services to other programs or devices, either in the same computer or over a computer network.
  • summary /ˈsʌm.ə.ɹi/ (zelfstandig naamwoord) — samenvatting, overzicht. An abstract or a condensed presentation of the substance of a body of material.
  • acquire /əˈkwaɪɚ/ (werkwoord) — verwerven, verkrijgen. To get.
  • fade /feɪd/ (werkwoord) — verzwakken, verslappen. To hit the ball with the shot called a fade.
  • talented /ˈtæləntɪd/ (bijvoeglijk naamwoord) — getalenteerd. Endowed with one or more talents.
  • framework /ˈfɹeɪm.wɜːk/ (zelfstandig naamwoord) — geraamte. A support structure comprising joined parts or conglomerated particles and intervening open spaces of similar or larger size.
  • technically /ˈtɛk.nɪˌkəl.i/ (bijwoord) — technisch gesproken, strikt genomen. Based on precise facts, which, however, may be contrary to common belief or casual terminology.
  • spectacular /spɛkˈtæk.jə.lɚ/ (bijvoeglijk naamwoord) — spectaculair. Amazing or worthy of special notice.
  • ironically /aɪˈɹɑnɪkli/ (bijwoord) — ironisch. In an ironic manner; in a way displaying irony.
  • programmer /ˈpɹoʊɡɹæmɚ/ (zelfstandig naamwoord) — programmeur. One who writes computer programs.
  • dependency /dɪˈpɛndənsi/ (zelfstandig naamwoord) — afhankelijkheid. A state of dependence; a refusal to exercise initiative.
  • meanwhile /ˈmiːnwaɪl/ (bijwoord) — intussen, ondertussen. During the time that something is happening, often specifically in a different place.
  • cloud /ˈklaʊ̯d/ (zelfstandig naamwoord) — wolk. A visible mass of water droplets suspended in the air.
  • infrastructure /ˈɪnfɹəˌstɹʌkt͡ʃə/ (zelfstandig naamwoord) — infrastructuur. An underlying base or foundation for a building, organization, or system.

Phrasal verbs die je zult horen

  • hand in (werkwoord) — inleveren, indienen. To give something to a responsible person.
  • shut down (werkwoord) — afsluiten, uitzetten. To close, terminate, or end; to stop operating, either permanently or temporarily.
  • take over (werkwoord) — overnemen. To assume control of something, such as a business or enterprise, and sometimes by force.

Uitspraak om op te letten

De spreker gebruikt 7 samentrekkingen en verkorte vormen, zoals didn't, you're, can't. Spreek ze kort uit, zoals je ze hoort.

  • De klanken “sh” en “zh”: transition /tɹænˈzɪʃ.ən/, capture /ˈkæp.(t)ʃɚ/, ownership /ˈoʊnɚʃɪp/, instruction /ɪnˈstɹʌkʃən/, authorization /ˌɔːθəɹaɪˈzeɪʃən/
  • Lange woorden — let op de klemtoon: developer /dɪˈvɛləpɚ/, technically /ˈtɛk.nɪˌkəl.i/, spectacular /spɛkˈtæk.jə.lɚ/, ironically /aɪˈɹɑnɪkli/, dependency /dɪˈpɛndənsi/

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, server, summary.

Grammatica in deze video

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

StructuurIn de video
Lijdende vorm be + voltooid deelwoord — het gaat om wat er gebeurt, niet om wie het doetbeen acquired · is built · is actually based
Present perfect have/has + voltooid deelwoord — iets uit het verleden dat nu nog teltthat's already been acquired · has been
Betrekkelijke bijzinnen who / which + zin — extra informatie over een persoon of dingFirefox, which is · Firefox, which was

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 →