Pratica di Shadowing: Did Anthropic Kill Git? - Impara a parlare inglese con i video

Scegli una modalità di pratica

Ogni modalità apre una sala di pratica a schermo intero.

65 frasi
Se le frasi sono troppo corte o troppo lunghe, clicca su Edit per modificarle.
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.

Scarica l'app

Tutto ciò che serve per parlare fluentemente

Pronuncia con IAVoto per ogni frase
Pratica IPAPadroneggia ogni suono
VocabolarioCostruisci il tuo lessico
Gioco di vocabolarioImpara giocando

Vocabolario e note di pronuncia per questa lezione

Questa lezione di conversazione si basa sul video “Did Anthropic Kill Git?”. Le parole che ritornano più spesso: Git, Anthropic, code, server, Claude. Questo video contiene 65 frasi e 881 parole da ripetere con lo shadowing. Il parlato dura 4:49. Chi parla va veloce, circa 183 parole al minuto: aspettati suoni legati e ridotti. Solo il 79% delle parole rientra nelle 3.000 più comuni dell’inglese, quindi il lessico è impegnativo.

Vocaboli chiave di questo video

15 parole del video che vale la pena imparare, con pronuncia e significato:

ParolaPronunciaSignificato
server sostantivo/ˈsɝvɚ/server
laptop sostantivo/ˈlæp.tɑp/notebook, laptop
merge verbo/mɝd͡ʒ/fondersi, unirsi
mirror sostantivo/ˈmiɹɚ/specchio
layer sostantivo/ˈleɪ̯ɚ/strato
commit verbo/kəˈmɪt/affidare, impegnarsi
developer sostantivo/dɪˈvɛləpɚ/sviluppatore, sviluppatrice
clone sostantivo/kloʊn/clone
checkout sostantivo/ˈt͡ʃɛkˌaʊt/check-out
cache sostantivo/kæʃ/nascondiglio, ripostiglio
chart sostantivo/t͡ʃɑɹt/carta, carta nautica
replacement sostantivo/ɹɪˈpleɪsmənt/sostituto, rimpiazzo
thread sostantivo/ˈθɹɛd/filo, refe
label sostantivo/ˈleɪ.bəl/etichetta
plain sostantivo/pleɪn/pianura

I phrasal verb che sentirai

ParolaPronunciaSignificato
check out verboinvestigare
go up verbosalire
keep up verbomantenere, conservare
pick up verbotirare su, sollevare
set up verbo/ˌsɛt ˈʌp/preparare, installare
split up verbodividersi

La grammatica di questo video

Le strutture che chi parla usa di più, con le parole esatte del video:

StrutturaNel video
Present perfect have/has + participio passato — un’azione passata che conta ancora adessohas replaced · has checked · has already posted
Forma passiva be + participio passato — conta ciò che accade, non chi lo fawere merged · was designed · were built

Pronuncia a cui fare attenzione

Chi parla usa 5 contrazioni e forme ridotte, come don't, can't, didn't. Pronunciale nella forma breve, così come le senti.

  • I suoni “th”: thread /ˈθɹɛd/, mathematics /mæθ(.ə)ˈmæt.ɪks/
  • I suoni “sh” e “zh”: cache /kæʃ/, measurement /ˈmɛʒ.ə.mənt/, shallow /ˈʃæloʊ/, unofficial /ʌn.əˈfɪʃ.əl/, shortcut /ˈʃɔːtkʌt/
  • Parole lunghe — attenzione all’accento: developer /dɪˈvɛləpɚ/, mathematics /mæθ(.ə)ˈmæt.ɪks/, internally /ɪnˈtɜːnəli/, unofficial /ʌn.əˈfɪʃ.əl/, repository /ɹɪˈpɒz.ɪ.t(ə.)ɹɪ/

I suoni difficili per chi parla italiano:

  • Consonante finale — senza aggiungere una vocale dopo: laptop /ˈlæp.tɑp/, merge /mɝd͡ʒ/, commit /kəˈmɪt/, checkout /ˈt͡ʃɛkˌaʊt/, cache /kæʃ/
  • /æ/ — più aperta della “e”: laptop /ˈlæp.tɑp/, cache /kæʃ/, mathematics /mæθ(.ə)ˈmæt.ɪks/, shallow /ˈʃæloʊ/, janky /ˈd͡ʒæŋ.kiː/

Come esercitarsi con questo video

  1. Ascolta tutto il video una volta senza parlare e annota le parole che non conosci.
  2. Inizia a velocità 0,75×, fai shadowing frase per frase e torna alla velocità normale quando diventa facile.
  3. Registrati e confronta con l’originale, facendo attenzione a parole come server, laptop, merge.

Cos'è la tecnica dello Shadowing?

Shadowing è una tecnica di apprendimento delle lingue supportata da studi scientifici, originariamente sviluppata per la formazione dei traduttori professionisti e resa popolare dal poliglotta Dr. Alexander Arguelles. Il metodo è semplice ma potente: ascolti un audio in inglese di madrelingua e lo ripeti immediatamente ad alta voce — come un'ombra che segue il parlante con un ritardo di solo 1–2 secondi. A differenza dell'ascolto passivo o degli esercizi di grammatica, lo shadowing costringe il tuo cervello e i muscoli della bocca a elaborare e riprodurre simultaneamente i modelli di discorso reale. La ricerca dimostra che migliora significativamente la precisione della pronuncia, l'intonazione, il ritmo, il discorso connesso, la comprensione dell'ascolto e la fluidità del parlato — rendendolo uno dei metodi più efficaci per la preparazione alla prova di speaking dell'IELTS e per la comunicazione reale in inglese.

Tecnica dello shadowing: leggi la guida completa passo dopo passo →