Small Teams, Clear Vision, Big Outcomes
Summary
Twitter's engineering team cut code from 700k to 70k lines, moved infrastructure on-prem, and reduced bills by 60% — proof that a small motivated team with clear direction can solve complex problems.
After a major restructuring, Twitter's engineering team reported striking results on their first anniversary:
- Reduced lines of code from 700k to 70k — a 90% reduction
- Reduced use of third-party cloud providers and moved most infrastructure on-prem
- Decreased infrastructure bill by 60%
Moving to on-prem is an unpopular choice in the tech industry, but it worked for their use case.
The lesson for engineering leaders
You do not need a big team to create an excellent product or innovate. A small, motivated team can solve big and complex problems when the leader has a clear vision on the problem the team should solve.
Team size and budget are inputs. Clarity of purpose and execution discipline are multipliers.
Related reading
How Software Engineering Teams Should Look in the AI Era
The traditional model repeats the same roles across siloed domain teams. The AI-era model connects specialized squads through an Efficiency Team building shared MCPs, RAG pipelines, agents, and agentic workflows.
Embeddings and Vector Databases: The Search Layer Behind Real AI Applications
Embeddings convert meaning into vectors; vector databases make those vectors searchable. Together they form the retrieval foundation behind RAG, semantic search, and enterprise AI assistants.
RAG vs Graph RAG vs Agentic RAG: How to Choose the Right Architecture
Standard RAG, Graph RAG, and Agentic RAG all connect LLMs to private data — but they solve different problems. Match the architecture to the question: retrieval, relationships, or reasoning.