Prática de Shadowing: Did Anthropic Kill Git? - Aprenda a falar inglês com vídeo

Escolha um modo de prática

Cada modo abre uma sala de prática em tela cheia.

65 frases
Se as frases estiverem muito curtas ou longas, clique em Edit para ajustá-las.
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.

Baixar aplicativo

Tudo o que você precisa para falar fluentemente

Pronúncia com IANota em cada frase
Prática de IPADomine cada som
VocabulárioMonte seu banco de palavras
Jogo de vocabulárioAprenda brincando

Vocabulário e dicas de fala para esta lição

Esta aula de conversação usa o vídeo “Did Anthropic Kill Git?”. As palavras que mais se repetem: Git, Anthropic, code, server, Claude. Este vídeo tem 65 frases e 881 palavras para praticar shadowing. A fala dura 4:49. O falante fala rápido, cerca de 183 palavras por minuto, então espere sons ligados e reduzidos. Apenas 79% das palavras estão entre as 3.000 mais comuns do inglês, por isso o vocabulário é exigente.

Vocabulário principal deste vídeo

15 palavras do vídeo que vale a pena aprender, com pronúncia e significado:

PalavraPronúnciaSignificado
server substantivo/ˈsɝvɚ/servidor, server
laptop substantivo/ˈlæp.tɑp/computador portátil, portátil
merge verbo/mɝd͡ʒ/unir, convergir
mirror substantivo/ˈmiɹɚ/espelho
layer substantivo/ˈleɪ̯ɚ/camada
developer substantivo/dɪˈvɛləpɚ/desenvolvedor, desenvolvedora
clone substantivo/kloʊn/clone
checkout substantivo/ˈt͡ʃɛkˌaʊt/caixa
cache substantivo/kæʃ/esconderijo
chart substantivo/t͡ʃɑɹt/carta náutica
replacement substantivo/ɹɪˈpleɪsmənt/substituto
thread substantivo/ˈθɹɛd/fio, linha
label substantivo/ˈleɪ.bəl/etiqueta, rótulo
plain substantivo/pleɪn/planície
suitable adjetivo[ˈsjuː.tə.bɫ̩]apropriado, favorável

Phrasal verbs que você vai ouvir

PalavraPronúnciaSignificado
check out verboverificar, sacar só
go up verbosubir
keep up verbomanter
pick up verbopegar
set up verbo/ˌsɛt ˈʌp/preparar

Gramática neste vídeo

As estruturas que o falante mais usa, com as palavras exatas do vídeo:

EstruturaNo vídeo
Present perfect have/has + particípio passado — uma ação passada que ainda importa agorahas replaced · has checked · has already posted
Voz passiva be + particípio passado — o foco está no que acontece, não em quem fazwere merged · was designed · were built

Pronúncia para ficar de olho

O falante usa 5 contrações e formas reduzidas, como don't, can't, didn't. Diga-as na forma curta, do jeito que você ouve.

  • Os sons de “th”: thread /ˈθɹɛd/, mathematics /mæθ(.ə)ˈmæt.ɪks/
  • Os sons de “sh” e “zh”: cache /kæʃ/, measurement /ˈmɛʒ.ə.mənt/, shallow /ˈʃæloʊ/, unofficial /ʌn.əˈfɪʃ.əl/, shortcut /ˈʃɔːtkʌt/
  • Palavras longas — acerte a sílaba tônica: developer /dɪˈvɛləpɚ/, mathematics /mæθ(.ə)ˈmæt.ɪks/, internally /ɪnˈtɜːnəli/, unofficial /ʌn.əˈfɪʃ.əl/, repository /ɹɪˈpɒz.ɪ.t(ə.)ɹɪ/

Sons difíceis para falantes de português:

  • Consoante final — sem acrescentar um “i” depois: laptop /ˈlæp.tɑp/, commit /kəˈmɪt/, checkout /ˈt͡ʃɛkˌaʊt/, chart /t͡ʃɑɹt/, replacement /ɹɪˈpleɪsmənt/
  • /l/ final — a língua toca o céu da boca, não vira “u”: label /ˈleɪ.bəl/, pile /paɪl/, unofficial /ʌn.əˈfɪʃ.əl/
  • s + consoante no início — sem um “i” antes: sparse /spɑːɹs/, swarm /swɔɹm/

Como praticar com este vídeo

  1. Ouça o vídeo inteiro uma vez sem falar e anote as palavras que você não conhece.
  2. Comece na velocidade 0,75×, faça shadowing frase por frase e volte à velocidade normal quando ficar fácil.
  3. Grave a sua voz e compare com o original, prestando atenção a palavras como server, laptop, merge.

O que é a Técnica de Shadowing?

Shadowing é uma técnica de aprendizado de idiomas com base científica, originalmente desenvolvida para o treinamento de intérpretes profissionais. O método é simples, mas poderoso: você ouve áudio em inglês nativo e repete imediatamente em voz alta — como uma sombra seguindo o falante com 1-2 segundos de atraso. Pesquisas mostram melhora significativa na precisão da pronúncia, entonação, ritmo, sons conectados, compreensão auditiva e fluência na fala.

Técnica de shadowing: leia o guia completo passo a passo →