Shadowing Practice: Did Anthropic Kill Git? - Learn English Speaking with Video

Kies een oefenmodus

Elke modus opent een volledig scherm oefenruimte.

65 zinnen
Als zinnen te kort of te lang zijn, klik op Bewerken om ze aan te passen.
1
Did Anthropic kill Git?
2
This week, a lot of people on X decided it did.
3
One post with over 600 ,000 views says Anthropic has replaced Git internally and the titans are falling.
4
Another says this is much bigger than it looks.
5
It all traces back to one post from Anthropic's own account, seen more than 6 .5 million times.
6
Part of the story is true.
7
Anthropic did stop using Git, but only for its own code, inside its own company.
8
Git itself is fine.
9
Anthropic keeps almost all of its code in one giant repository, a monorepo.
10
In May, about 2 ,500 changes were merged into it every day.
11
By September, it was over 30 ,000 a day.
12
On September 9th alone, 30 ,401 changes went in.
13
Their chart even has a dip in late July labeled the quiet week, and right after it, the line goes almost straight up.
14
Claude writes a lot of that code, and Anthropic says every bottleneck they remove leads to even more of it.
15
At that rate, the repository got heavy.
16
The history of the main branch alone is almost 100 gigabytes.
17
Their CI system checks out the code about 25 million times a day before you count developers, agent sandboxes, and research jobs.
18
Anthropic did the maths.
19
If every one of those checkouts fetched the repo the normal way, that would be over 600 petabytes of Git traffic every day.
20
Git was designed for a different kind of user.
21
Every clone is a full copy of the repository with all of its history, and it can do almost everything offline.
22
That's great for a person on a laptop on a plane.
23
At Anthropic, almost every client is an agent or a CI job, and those are always online.
24
They tried the usual fixes first, like shallow clones and sparse checkouts.
25
At the peak, they were running several hundred internal Git mirrors just to keep up.
26
So they built their own.
27
It's called Scion, and it moves the work from your machine to the server.
28
Commits, merges, rebases, blame, and history all happen on the server so there's nothing to push.
29
The client keeps a small cache and only downloads the files it actually reads.
30
A CI job that needs a diff can ask the server for it and never check out the code at all.
31
Between the client and the server sit two layers of caches, one on every machine and one in every region.
32
And each layer answers over 99 % of requests by itself.
33
Anthropic says it borrowed ideas from Google's Piper and Meta's Sapling, which were built for huge human teams.
34
On a developer machine, Git status took almost four seconds, and Scion does it in 19 milliseconds.
35
For agents, setting up a fresh work tree went from seven minutes to five seconds.
36
The whole system uses about 200 times less CPU and memory than the old mirrors, and CI got a quarter of its CPU back.
37
These are Anthropic's own measurements, and nobody outside the company has checked them yet seven people built it.
38
In five months, they made Scion, a code review tool called Antique, and a few other systems,
39
and they moved the whole monorepo over while the merge rate went up 10 times.
40
Claude wrote a lot of that code too.
41
The team had handwritten a pipeline to import the old Git history,
42
and an early version of Claude Mythos rewrote it to use 20 times less memory and run four times faster.
43
Every engineer on the project now rates Claude as better at writing code than they are.
44
They also say a big part of their job became telling Claude no
45
when it took shortcuts or piled on checks nobody needed.
46
On Hacker News, the thread passed 800 points and 900 comments in a day.
47
The most replied comment says that every time the writer stops reviewing Claude's code, they later find janky crap.
48
Others said a central server you always have to reach sounds a lot like subversion or perforce.
49
The older systems get replaced.
50
One person asked why Anthropic didn't just split up the monorepo.
51
On X, Dex Horthy pointed at the trade -off most people will feel.
52
Today, if GitHub is down, you can still commit on your laptop.
53
With Scion, if the server is down, you can't.
54
So did Anthropic kill Git?
55
No. In their own words, Scion is by no means a suitable replacement for Git for general use.
56
They say it only makes sense for truly enormous repos, with tens of thousands of engineers or swarms of agents.
57
It isn't open source and they don't plan to release it.
58
Your repos on GitHub don't change, and Claude code still works with plain Git.
59
A small team has already posted an unofficial open source version, but Anthropic has nothing to do with it.
60
What Anthropic wants is for Git to pick up some of these ideas,
61
like servers that do more of the work and answer questions about history through an API.
62
They say they want to build that with GitHub, GitLab, and the open source community,
63
and they expect other companies using AI coding tools to hit the same wall within a year.
64
If that happens, the changes will most likely land on the server side,
65
and the Git on your laptop will keep working the way it does today.

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 is gebaseerd op de video “Did Anthropic Kill Git?”. Deze woorden komen het vaakst terug: Git, Anthropic, code, server, Claude. Deze video bevat 65 zinnen en 881 woorden om na te spreken. Het gesproken deel duurt 4:49. De spreker praat snel, ongeveer 183 woorden per minuut, dus reken op verbonden en ingeslikte klanken. Slechts 79% van de woorden hoort bij de 3.000 meest gebruikte Engelse woorden, dus de woordenschat is pittig.

Belangrijke woorden in deze video

15 woorden uit de video die het leren waard zijn, met uitspraak en betekenis:

WoordUitspraakBetekenis
server zelfstandig naamwoord/ˈsɝvɚ/server
laptop zelfstandig naamwoord/ˈlæp.tɑp/laptop, notebook
merge werkwoord/mɝd͡ʒ/samenvoegen, fuseren
mirror zelfstandig naamwoord/ˈmiɹɚ/spiegel
layer zelfstandig naamwoord/ˈleɪ̯ɚ/laag
commit werkwoord/kəˈmɪt/toevertrouwen, toewijzen
developer zelfstandig naamwoord/dɪˈvɛləpɚ/ontwikkelaar, ontwerper
clone zelfstandig naamwoord/kloʊn/kloon
checkout zelfstandig naamwoord/ˈt͡ʃɛkˌaʊt/kassa
cache zelfstandig naamwoord/kæʃ/cache
replacement zelfstandig naamwoord/ɹɪˈpleɪsmənt/vervanger, plaatsvervanger
thread zelfstandig naamwoord/ˈθɹɛd/draad, garen
label zelfstandig naamwoord/ˈleɪ.bəl/etiket, label
plain zelfstandig naamwoord/pleɪn/vlakte
suitable bijvoeglijk naamwoord[ˈsjuː.tə.bɫ̩]geschikt, passend

Phrasal verbs die je zult horen

WoordUitspraakBetekenis
check out werkwoordonderzoeken
keep up werkwoordbijblijven
pick up werkwoordoppakken, optillen
set up werkwoord/ˌsɛt ˈʌp/bereiden, voorbereiden

Grammatica in deze video

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

StructuurIn de video
Present perfect have/has + voltooid deelwoord — iets uit het verleden dat nu nog telthas replaced · has checked · has already posted
Lijdende vorm be + voltooid deelwoord — het gaat om wat er gebeurt, niet om wie het doetwere merged · was designed · were built

Uitspraak om op te letten

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

  • De “th”-klanken: thread /ˈθɹɛd/, mathematics /mæθ(.ə)ˈmæt.ɪks/
  • De klanken “sh” en “zh”: cache /kæʃ/, measurement /ˈmɛʒ.ə.mənt/, shallow /ˈʃæloʊ/, unofficial /ʌn.əˈfɪʃ.əl/, shortcut /ˈʃɔːtkʌt/
  • Lange woorden — let op de klemtoon: developer /dɪˈvɛləpɚ/, mathematics /mæθ(.ə)ˈmæt.ɪks/, internally /ɪnˈtɜːnəli/, unofficial /ʌn.əˈfɪʃ.əl/, repository /ɹɪˈpɒz.ɪ.t(ə.)ɹɪ/

Klanken die Nederlandstaligen lastig vinden:

  • Stemhebbende eindmedeklinker — /b/, /d/, /g/, /z/, /v/ niet verscherpen: merge /mɝd͡ʒ/, thread /ˈθɹɛd/, millisecond /ˈmɪlɪˌsɛkənd/
  • /æ/ — opener dan de Nederlandse “e”: laptop /ˈlæp.tɑp/, cache /kæʃ/, mathematics /mæθ(.ə)ˈmæt.ɪks/, shallow /ˈʃæloʊ/, janky /ˈd͡ʒæŋ.kiː/

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 server, laptop, merge.

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 →