Shadowing-Übung: Did Anthropic Kill Git? - Englisch Sprechen Lernen mit Video
Übungsmodus wählen
Jeder Modus öffnet einen Übungsraum im Vollbild.
65 Sätze
Wenn Sätze zu kurz oder zu lang sind, klicke auf Edit, um sie anzupassen.
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 herunterladen
Alles, was du zum fließenden Sprechen brauchst
KI-AussprachebewertungJeder Satz bewertet
IPA-TrainingJeden Laut meistern
WortschatzBaue deinen Wortschatz auf
VokabelspielSpielend lernen
FOR YOU
Empfohlenes Video
C11
78 Sätze
The easy way to keep your repos tidy.
Daily ConversationUniversity StudentsWorking Adults
C13
63 Sätze
A $6.3 billion open-weight model just got embarrassed by the French...
Daily ConversationUniversity StudentsWorking Adults
C11
202 Sätze
Is React Native Dead? Shopify Is Leaving
Daily ConversationUniversity StudentsWorking Adults
C13
234 Sätze
The Philosophy of Rick Sanchez
Daily ConversationUniversity StudentsWorking Adults
C13
182 Sätze
How Did Ancient Humans Survive the Deadliest Predators on Earth?
Daily ConversationUniversity StudentsWorking Adults
C11
207 Sätze
Go’s Big Mistake
Daily ConversationUniversity StudentsWorking Adults
C11
215 Sätze
Creator of C# and TypeScript: "AI will NEVER Replace Coders, Here's Why" | Anders Hejlsberg
Daily ConversationUniversity StudentsWorking Adults
C16
51 Sätze
Linux got wrecked by backdoor attack
American AccentDaily ConversationUniversity StudentsWorking Adults
C11
68 Sätze
GitHub Copilot now controls your command line...
Daily ConversationUniversity StudentsWorking Adults
C132 Sätze
Linus Torvalds Explains What Makes Linux So Fast
Daily ConversationUniversity StudentsWorking Adults
C13
173 Sätze
STOP Running Code On Your Computer
Daily ConversationUniversity StudentsWorking Adults
C12
182 Sätze
We Let $200 GPT-Pro Think for 7 Days on Unsolved Math
Daily ConversationUniversity StudentsWorking Adults
Wortschatz und Sprechhinweise zu dieser Lektion
Diese Sprechübung basiert auf dem Video „Did Anthropic Kill Git?“. Diese Wörter kommen am häufigsten vor: Git, Anthropic, code, server, Claude. Dieses Video enthält 65 Sätze und 881 Wörter zum Nachsprechen. Der gesprochene Teil dauert 4:49. Der Sprecher spricht schnell, etwa 183 Wörter pro Minute – rechne mit verbundenen und verkürzten Lauten. Nur 79 % der Wörter gehören zu den 3.000 häufigsten im Englischen, der Wortschatz ist also anspruchsvoll.
Wichtiger Wortschatz in diesem Video
15 lernenswerte Wörter aus dem Video, mit Aussprache und Bedeutung:
| Wort | Aussprache | Bedeutung |
|---|---|---|
| server Substantiv | /ˈsɝvɚ/ | Server |
| laptop Substantiv | /ˈlæp.tɑp/ | Laptop, Klapprechner |
| merge Verb | /mɝd͡ʒ/ | zusammenlegen, zusammenfügen |
| mirror Substantiv | /ˈmiɹɚ/ | Spiegel |
| layer Substantiv | /ˈleɪ̯ɚ/ | Lage, Schicht |
| commit Verb | /kəˈmɪt/ | anvertrauen, (vertrauensvoll) übergeben |
| developer Substantiv | /dɪˈvɛləpɚ/ | Entwickler, Entwicklerin |
| clone Substantiv | /kloʊn/ | Klon |
| checkout Substantiv | /ˈt͡ʃɛkˌaʊt/ | Kasse, Supermarktkasse |
| cache Substantiv | /kæʃ/ | Cache, Zwischenspeicher |
| chart Substantiv | /t͡ʃɑɹt/ | Karte |
| replacement Substantiv | /ɹɪˈpleɪsmənt/ | Ersatz, Ersatzspieler |
| thread Substantiv | /ˈθɹɛd/ | Faden, Garn |
| label Substantiv | /ˈleɪ.bəl/ | Etikett, Etikette |
| plain Substantiv | /pleɪn/ | Ebene |
Phrasal Verbs, die du hören wirst
| Wort | Aussprache | Bedeutung |
|---|---|---|
| check out Verb | überprüfen | |
| go up Verb | hinaufgehen, steigen | |
| keep up Verb | erhalten | |
| pick up Verb | aufheben, aufnehmen | |
| set up Verb | /ˌsɛt ˈʌp/ | aufbauen, für den Einsatz vorbereiten |
Grammatik in diesem Video
Die Strukturen, die der Sprecher am häufigsten verwendet, mit den genauen Worten aus dem Video:
| Struktur | Im Video |
|---|---|
| Present Perfect have/has + Partizip Perfekt – eine vergangene Handlung, die jetzt noch wichtig ist | has replaced · has checked · has already posted |
| Passiv be + Partizip Perfekt – wichtig ist, was geschieht, nicht wer es tut | were merged · was designed · were built |
Aussprache, auf die du achten solltest
Der Sprecher verwendet 5 Kurzformen und abgeschwächte Formen, zum Beispiel don't, can't, didn't. Sprich sie in der kurzen Form, so wie du sie hörst.
- Die „th“-Laute: thread /ˈθɹɛd/, mathematics /mæθ(.ə)ˈmæt.ɪks/
- Die Laute „sh“ und „zh“: cache /kæʃ/, measurement /ˈmɛʒ.ə.mənt/, shallow /ˈʃæloʊ/, unofficial /ʌn.əˈfɪʃ.əl/, shortcut /ˈʃɔːtkʌt/
- Lange Wörter – auf die Betonung achten: developer /dɪˈvɛləpɚ/, mathematics /mæθ(.ə)ˈmæt.ɪks/, internally /ɪnˈtɜːnəli/, unofficial /ʌn.əˈfɪʃ.əl/, repository /ɹɪˈpɒz.ɪ.t(ə.)ɹɪ/
Laute, die Deutschsprachigen schwerfallen:
- Stimmhafter Auslaut — /b/, /d/, /g/, /z/, /v/ am Wortende nicht verhärten: merge /mɝd͡ʒ/, thread /ˈθɹɛd/, millisecond /ˈmɪlɪˌsɛkənd/
- /æ/ — offener als „ä“: laptop /ˈlæp.tɑp/, cache /kæʃ/, mathematics /mæθ(.ə)ˈmæt.ɪks/, shallow /ˈʃæloʊ/, janky /ˈd͡ʒæŋ.kiː/
- /dʒ/ — stimmhaft, nicht „tsch“: merge /mɝd͡ʒ/, janky /ˈd͡ʒæŋ.kiː/
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 server, laptop, merge.
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.