What Did George Hotz Say About Twitter's Code Challenges?

TL;DR

George Hotz highlights that Twitter's code complexities arise from a promotion system favoring the creation of custom solutions over established ones. He emphasizes the need for strong technical leadership that values simplicity and transparency, akin to Elon Musk's approach. Refactoring should start with building tests to enhance code reliability while gradually streamlining components.

Transcript

what other stuff can you say about the code base that made it difficult uh like what are some interesting sort of quirks broadly speaking from that compared to just your experience with comma and everywhere else the real thing that I spoke to a bunch of uh you know like like individual contributors to Twitter and I just I had staffed I'm like okay ... Read More

Key Insights

• 🥺 Incentives in promotion systems can lead to unnecessary code and complexity in a codebase.
• ❓ Technical leadership and the ability to recognize simplicity are crucial in creating a great codebase.
• 🍃 Transparency and clear values in company leadership can create a productive dictatorship where employees have the choice to either opt in or leave.
• 🥶 Refactoring codebases requires a focus on building tests and gradually replacing old components.
• 🧑‍🏭 The timing and approach to refactoring depend on various factors such as product profitability and maintaining reliability.
• 👨‍💻 Codebases should prioritize simplicity, smaller code size, and elegant ideas.
• ↘️ Dictatorship-style leadership can be effective if the leader has the right values and provides benefits like lower costs and increased innovation.
• 🎙️ More videos with George Hotz / Elon Musk's:
  • Ep 18: Petaflops to the People — with George Hotz of tinycorp
  • George Hotz | Programming | can tinygrad run the openpilot model? | g…
  • Comma.ai Drive and Tour with George Hotz and Lex Fridman

Questions & Answers

Q: How did Twitter's promotion system lead to a complex codebase?

Twitter's promotion system incentivized developers to create replacement libraries instead of using existing ones like nginx, resulting in unnecessary code and complexity.

Q: How does the author promote simplicity in codebases at companies like comma and tiny corp?

The author encourages developers to explain their code and if a simpler solution is found, it is rewritten. Technical leadership is crucial in recognizing and implementing simplicity.

Q: How does the author approach codebase refactoring at Twitter?

The author suggests starting with building tests and ensuring trust in the codebase, then allowing developers to rewrite modules in any language as long as the tests pass. Simplification and replacing old components are prioritized.

Q: How does the author integrate testing in a codebase with few tests at Twitter?

The author proposes a similar approach to what they use at comma, where they have a process replay system. They suggest writing new tests for modules and gradually replacing and improving the codebase.

Summary & Key Takeaways

• The codebase at Twitter had quirks and complexities because promotions were based on creating widely-used libraries, leading to unnecessary replacements and bloated code.

• In order to create a great codebase, technical leadership and the ability to recognize simplicity are essential, along with managers who have deep technical knowledge.

• The author explains the importance of a transparent dictatorship with clear values and the ability to opt out, similar to Elon Musk's leadership style.