Listen & Follow Along — Article Summary
Article Summary
Anthropic, a large tech company, recently faced a big problem. Their AI tools, like Claude, helped engineers write code much faster than before. Because of this, the number of code changes they merged each day grew very quickly, from 2,500 to over 30,000 in just four months. This rapid growth created a bottleneck in their existing systems, especially their source control system, Git. Git was not built to handle such a high volume of daily changes and was slowing down their work. It was designed assuming that users would sometimes work offline, but Anthropic's engineers are always online, which made Git inefficient for them. Also, Git could not easily scale up to meet their growing needs, even with many mirror copies.
To solve this, Anthropic decided to build its own custom source control system, which they call 'Scion.' They also created a new code review system, 'Antique,' because they could no longer use GitHub's tools. This was a huge migration of all their code off Git. They chose to store their code changes in Google Spanner and large files in Google Cloud Storage, which are very reliable systems. A small team of seven engineers built and now maintains this new infrastructure. This shows that even big, standard tools like Git can be insufficient when a company's needs become unique and grow extremely fast.
Interestingly, Anthropic is not the first big tech company to do this. Google and Meta also built their own internal source control systems, 'Piper' and 'Sapling,' many years ago for similar reasons. They found that Git could not handle their massive monorepos or the sheer amount of code their engineers produced. However, there is a controversy about Anthropic's Scion. The creator of an open-source server called Mononoke has accused Anthropic of copying its design without giving proper credit. Anthropic later added a small attribution, saying their goal was to share learnings, not to show off new ideas. This situation makes us think about whether companies should always create their own tools or work to improve existing ones.
Key Vocabulary
bottleneck
/ˈbɑːtəlnɛk/
Click to reveal
volume
Click to reveal
scale
/skeɪl/
Click to reveal
custom
/ˈkʌstəm/
Click to reveal
migration
/maɪˈɡreɪʃən/
Click to reveal
infrastructure
/ˈɪnfrəˌstrʌktʃər/
Click to reveal
monorepo
Click to reveal
controversy
Click to reveal
attribution
Click to reveal
Comprehension Questions
1. What was the main reason Anthropic decided to build its own source control system?
- Git was too expensive for them to use.
- They wanted to work offline more often.
- Git could not handle their very fast-growing amount of code changes.
- They needed a system that only worked with Google products.
2. Which other large tech companies mentioned in the article also built their own internal source control systems?
- Apple and Microsoft
- Amazon and Netflix
- Google and Meta
- IBM and Oracle
3. Why did Anthropic's rapid increase in code changes create a 'bottleneck'?
- Their engineers became too slow at writing code.
- The standard tools like Git were not designed for such a high speed and volume of work.
- They stopped using AI tools to help write code.
- They had too many people working on the same project.
4. What does the article suggest about the relationship between Anthropic and the creator of Mononoke?
- They worked together to build Scion.
- The Mononoke creator was upset because they believed Anthropic copied their design without credit.
- The Mononoke creator offered to help Anthropic with their new system.
- They had a friendly competition to build the best system.
5. Based on the article, when might it be a good idea for a company to build a custom tool instead of using a standard one?
- Only when they have a very small budget.
- When standard tools are too difficult to learn.
- When their specific needs grow so large or unique that existing standard tools cannot handle them.
- If they want to keep all their work a secret from other companies.
Discussion Prompts
1. Have you ever experienced a situation in your work where a standard tool or process was not good enough for your team's specific needs? What did you do?
2. Do you think it's always better for a company to build its own custom solutions, or should it try to adapt existing ones? Why?
3. How important is it to give credit or attribution when you use ideas or designs from others in your professional projects? Have you seen this happen in your field?
Live Session Prep & Cheat Sheet
🎯 Speaking Targets (Vocabulary)
Try to use these target terms in your speaking turns:
- bottleneck
- scale
- custom
- migration
- infrastructure
⚙️ Grammar Target Formula
Talking About Past Habits and Present Changes: 'Used to' and 'No longer': Subject + used to + Verb (base form) / Subject + no longer + Verb (present)
💬 Discussion Openers
Use these phrases to open or structure your arguments:
- In my experience...
- I think this article shows that...
- One point I find interesting is...
- What are your thoughts on...?
Teacher Notes
This lesson explores how companies deal with rapid growth and technological challenges. Encourage students to connect the article's themes to their own professional experiences. Pay attention to the correct usage of 'used to' and 'no longer' in speaking exercises. The controversy section can lead to interesting ethical discussions.
Speaking Class Facilitation Guide (Tutors/Moderators Only)
🎭 Role-Play Scenario
Situation: Your company's current project management software is too slow and crashes often because your team has grown a lot. You need to decide whether to buy a new standard software or invest in building a custom one.
Project Manager: You prefer to buy a new standard software because it's usually cheaper and faster to implement. You worry about the cost and time of building a custom system.
Head of IT: You believe a custom software would be better in the long run because it would perfectly fit the team's unique needs, even if it costs more and takes longer to develop at first.
Goal: Discuss the pros and cons of both options and decide which path to take for the company.
⚖️ Debate Prompt
Question: Should companies always try to use existing tools, or is it better to build custom solutions when facing big challenges?
Side A:
- Existing tools are cheaper and faster to start using.
- Many existing tools are very good and offer wide support.
- Building custom tools is expensive and takes a lot of time and resources.
Side B:
- Custom solutions can fit unique company needs perfectly.
- They can give a company a competitive advantage.
- If a standard tool doesn't scale, it can slow down the whole company.
💡 Discussion Facilitation Tips
Encourage students to use the target vocabulary and grammar points during the role-play and debate. Ask 'why' after opinions to push for deeper explanations and reasoning. Gently correct errors in 'used to' and 'no longer' usage, and ask students to rephrase.