Breaking it down with Ian Brown

Oxide and Friends · 27 Dec 2022 · 1h 25m · Episode 39

What this episode covers

Ian Brown, a former Twitter engineering manager, and Theo, a security expert, join Bryan Cantrill and Adam Leventhal to analyze a viral Twitter Space where Elon Musk proposed a total rewrite of Twitter's infrastructure. Brown and the hosts dismantle Musk's claim that the existing stack is 'crazy' by highlighting the 'Ship of Theseus' nature of the code, the value of hard-won engineering decisions, and the fact that Twitter's innovation bottlenecks were organizational, not technical. They contrast Musk's lack of curiosity and fear-based leadership with the necessary conditions for successful software development, using historical examples like Steve Jobs' return to Apple and the ZFS rewrite to illustrate the dangers of 'second system syndrome' and the importance of paying down technical debt through reform rather than revolution.

Mentioned

Companies
Twitter, Apple
Products
Next, ZFS, Mesos, Aurora, Docker, Kubernetes
Also
Elon Musk, Ian Brown, George Hotz, Theo, Bryan Cantrill, Adam Leventhal, Steve Jobs, Jeff Bonwick, GCP, AWS, Rust, Linux

Other shows on the same ground, closest first.

  • Embedded.fm · 1h 07m

    78: Happy Cows

    Chris Svec, a senior principal software engineer at iRobot, discusses his concept of 'empathy-driven development' for embedded software teams. He argues that engineers should write code with empathy for future maintainers, new hires, and their own future selves, rather than focusing solely on the 'lone hacker' archetype. Svec highlights how imposter syndrome and the 'rock star' mentality hinder collaboration, and suggests that treating code as readable fiction for multiple audiences can improve team dynamics and product quality.

  • Embedded.fm · 1h 07m

    78: Happy Cows (Repeat)

    Chris Svec, a senior principal software engineer at iRobot, discusses his concept of 'empathy-driven development,' arguing that software engineers should write code with empathy for future maintainers, new hires, and their own future selves. He connects this mindset to combating imposter syndrome and overcoming the 'lone hacker' culture prevalent in engineering education and industry. Svec also shares insights from his work on the Next Generation Roomba and recommends books like 'Thinking, Fast and Slow' and 'Make It Stick' to understand cognitive psychology in learning and communication.

  • Over the Air · 37m

    Moonshot Engineering Projects: Getting Innovative Initiatives Off the Ground

    Luke Wilhelm, former head of hardware for Uber’s flying car project (Uber Elevate) and current Chief Product Officer at Very, shares advice on leading high-stakes engineering initiatives. He emphasizes building high-quality teams, managing up with honest risk assessments, and the strategic use of saying 'no' to eliminate non-essential features. Wilhelm draws on his experience at Apple, Quantumscape, and Greencharge Networks to discuss the dangers of rationalization and the importance of empathy in leadership.

  • Embedded.fm · 1h 13m

    290: Rule of Thumbs

    Phillip Johnston, founder of Embedded Artistry, discusses embedded software consulting, the importance of upfront design to avoid costly rewrites, and best practices for code reviews and testing. He analyzes the Boeing 737 MAX crashes as a systemic failure driven by business pressures and poor risk analysis, and explains the challenges of retargeting C++ standard libraries like libc++ to RTOS environments such as FreeRTOS and ThreadX.

  • The Pragmatic Embedded Podcast · 43m

    2024 christmas special

    Hosts Jeff Gable and Luca Eden reflect on three years of The Pragmatic Embedded Podcast, highlighting guests like Miro Slavic, John Odo, and Luca Mustafa who pushed specific technical and process boundaries. They discuss the disconnect between senior engineers seeking agile change and managers resistant to the hard work required for true transformation. The conversation emphasizes that successful embedded development requires breaking the 'Iron Triangle' of fixed scope, time, and budget by prioritizing core functionality and asking difficult questions about deadlines.

The summary, chapters and topics are generated from the episode’s audio by this directory, not written by Oxide and Friends. The episode itself belongs to its publisher.