Shadowing Practice: Did Anthropic Kill Git? - Learn English Speaking with Video
Elige un modo de práctica
Cada modo abre una sala de práctica a pantalla completa.
65 oraciones
Si las oraciones son demasiado cortas o largas, haz clic en Editar para ajustarlas.
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.
Descargar app
Todo lo que necesitas para hablar con fluidez
Pronunciación con IAEvalúa cada oración
Práctica de IPADomina cada sonido
VocabularioConstruye tu banco de palabras
Juego de vocabularioAprende mientras juegas
✨ Recomendar Video
C11
78 oraciones
The easy way to keep your repos tidy.
Daily ConversationUniversity StudentsWorking Adults
C13
63 oraciones
A $6.3 billion open-weight model just got embarrassed by the French...
Daily ConversationUniversity StudentsWorking Adults
C11
202 oraciones
Is React Native Dead? Shopify Is Leaving
Daily ConversationUniversity StudentsWorking Adults
C13
234 oraciones
The Philosophy of Rick Sanchez
Daily ConversationUniversity StudentsWorking Adults
C13
182 oraciones
How Did Ancient Humans Survive the Deadliest Predators on Earth?
Daily ConversationUniversity StudentsWorking Adults
C11
207 oraciones
Go’s Big Mistake
Daily ConversationUniversity StudentsWorking Adults
C11
215 oraciones
Creator of C# and TypeScript: "AI will NEVER Replace Coders, Here's Why" | Anders Hejlsberg
Daily ConversationUniversity StudentsWorking Adults
C16
51 oraciones
Linux got wrecked by backdoor attack
American AccentDaily ConversationUniversity StudentsWorking Adults
C11
68 oraciones
GitHub Copilot now controls your command line...
Daily ConversationUniversity StudentsWorking Adults
C132 oraciones
Linus Torvalds Explains What Makes Linux So Fast
Daily ConversationUniversity StudentsWorking Adults
C13
173 oraciones
STOP Running Code On Your Computer
Daily ConversationUniversity StudentsWorking Adults
C12
182 oraciones
We Let $200 GPT-Pro Think for 7 Days on Unsolved Math
Daily ConversationUniversity StudentsWorking Adults
Vocabulario y notas de pronunciación para esta lección
Esta lección de conversación se basa en el vídeo “Did Anthropic Kill Git?”. Las palabras que más se repiten: Git, Anthropic, code, server, Claude. Este vídeo tiene 65 frases y 881 palabras para practicar shadowing. La parte hablada dura 4:49. El hablante habla rápido, unas 183 palabras por minuto, así que espera sonidos enlazados y reducidos. Solo el 79 % de las palabras está entre las 3.000 más comunes del inglés, por lo que el vocabulario es exigente.
Vocabulario clave de este vídeo
15 palabras del vídeo que vale la pena aprender, con su pronunciación y significado:
| Palabra | Pronunciación | Significado |
|---|---|---|
| server sustantivo | /ˈsɝvɚ/ | servidor |
| laptop sustantivo | /ˈlæp.tɑp/ | portátil, computador portátil |
| merge verbo | /mɝd͡ʒ/ | mergear |
| mirror sustantivo | /ˈmiɹɚ/ | espejo |
| layer sustantivo | /ˈleɪ̯ɚ/ | capa, tongada |
| commit verbo | /kəˈmɪt/ | encomendar |
| developer sustantivo | /dɪˈvɛləpɚ/ | desarrollador |
| clone sustantivo | /kloʊn/ | clon |
| checkout sustantivo | /ˈt͡ʃɛkˌaʊt/ | caja |
| cache sustantivo | /kæʃ/ | memoria caché, caché |
| chart sustantivo | /t͡ʃɑɹt/ | chart |
| replacement sustantivo | /ɹɪˈpleɪsmənt/ | reemplazo, remplazo |
| thread sustantivo | /ˈθɹɛd/ | hilo, bouclé (buclé) |
| label sustantivo | /ˈleɪ.bəl/ | etiqueta, rótulo |
| plain sustantivo | /pleɪn/ | llanura, planicie |
Phrasal verbs que vas a escuchar
| Palabra | Significado |
|---|---|
| check out verbo | investigar, chequear |
| go up verbo | subir |
| keep up verbo | continuar con, continuar así |
| pick up verbo | coger, asir |
| split up verbo | desparejarse, separarse |
Gramática en este vídeo
Las estructuras que más usa el hablante, con las palabras exactas del vídeo:
| Estructura | En el vídeo |
|---|---|
| Present perfect have/has + participio pasado — una acción pasada que sigue importando ahora | has replaced · has checked · has already posted |
| Voz pasiva be + participio pasado — importa lo que ocurre, no quién lo hace | were merged · was designed · were built |
Pronunciación a tener en cuenta
El hablante usa 5 contracciones y formas reducidas, como don't, can't, didn't. Dilas en su forma corta, tal como las oyes.
- Los sonidos de “th”: thread /ˈθɹɛd/, mathematics /mæθ(.ə)ˈmæt.ɪks/
- Los sonidos de “sh” y “zh”: cache /kæʃ/, measurement /ˈmɛʒ.ə.mənt/, shallow /ˈʃæloʊ/, unofficial /ʌn.əˈfɪʃ.əl/, shortcut /ˈʃɔːtkʌt/
- Palabras largas — cuida el acento: developer /dɪˈvɛləpɚ/, mathematics /mæθ(.ə)ˈmæt.ɪks/, internally /ɪnˈtɜːnəli/, unofficial /ʌn.əˈfɪʃ.əl/, repository /ɹɪˈpɒz.ɪ.t(ə.)ɹɪ/
Sonidos difíciles para hispanohablantes:
- s + consonante al inicio — sin añadir una “e” delante: sparse /spɑːɹs/, swarm /swɔɹm/
- /v/ — no es /b/: los dientes tocan el labio inferior: server /ˈsɝvɚ/, developer /dɪˈvɛləpɚ/, subversion /sʌ̈bˈvɝ.ʒən/
- /dʒ/ — no es la “y” ni la “ch”: merge /mɝd͡ʒ/, janky /ˈd͡ʒæŋ.kiː/
Cómo practicar con este vídeo
- Escucha el vídeo entero una vez sin hablar y anota las palabras que no conoces.
- Empieza a velocidad 0,75×, haz shadowing frase por frase y vuelve a la velocidad normal cuando te resulte fácil.
- Grábate y compara con el original, prestando atención a palabras como server, laptop, merge.
¿Qué es la Técnica de Shadowing?
Shadowing es una técnica de aprendizaje de idiomas respaldada por la ciencia, desarrollada originalmente para la formación de intérpretes profesionales y popularizada por el políglota Dr. Alexander Arguelles. El método es simple pero poderoso: escuchas audio en inglés nativo y lo repites en voz alta de inmediato, como una sombra que sigue al hablante con solo 1-2 segundos de retraso. A diferencia de la escucha pasiva o los ejercicios de gramática, el shadowing obliga a tu cerebro y músculos de la boca a procesar y reproducir simultáneamente patrones de habla reales. Las investigaciones muestran que mejora significativamente la precisión de la pronunciación, la entonación, el ritmo, el habla conectada, la comprensión auditiva y la fluidez al hablar, convirtiéndola en una de las metodologías más efectivas para la preparación del IELTS Speaking y la comunicación en inglés en el mundo real.