“If you think good architecture is expensive, try bad architecture.”— Brian Foote, Software researcher specializing in reusable patterns
A few weeks ago, my wonderful Fiat 500 Convertible EV autonomously decided to update its software after a brief stop in the middle of upper Bavaria. Black screens apart from a stern warning to not drive on. No option to defer the update.
Unfortunately, I was on my way to TH Rosenheim to give a full day of lectures. So I decided to go into override mode and pressed the “Start” button nevertheless. Motors, steering, and braking seemed to work and so I continued my journey. And, alas, just before turning into the university’s parking lot, the displays came back on.
Apparently, this car is not fully software-defined (maybe it has rather independent ECUs), or so it would seem.
This week’s podcast episode explores the shift in the automotive industry toward software-defined vehicles (SDVs), with a focus on the distinct approaches to software development adopted by Tesla and Rivian. Jane and Austin discuss how modern cars are increasingly defined by software rather than mechanical engineering, with Tesla adopting a near-total in-house software development strategy and Rivian opting for about 80% internal development complemented by carefully chosen strategic partnerships.
The discussion highlights the implications of this shift on traditional automotive power structures, supply chains, and the role of original equipment manufacturers (OEMs). Key points include the strategic advantages of in-house software development, such as faster innovation and data-driven improvements, as well as the challenges, including high R&D costs and the need for robust cybersecurity measures.
Our hosts also explore the software development cultures, tools, and technologies used by Tesla and Rivian, comparing them to those employed by major tech companies such as Google and Meta. The episode concludes by considering the future impact of software-defined vehicles on car ownership and the skills required for building and maintaining these complex machines.
Highlights:
- The Rise of Software-Defined Vehicles
- Defining the Software-Defined Vehicle (SDV)
- Tesla’s In-House Software Philosophy
- Tesla’s Software Development Practices
- Tesla’s Key Software Domains
- Rivian’s Focused Software Approach
- Rivian’s Software Development Culture and Tools
- Rivian’s Key Software Domains
- Comparing Tesla’s and Rivian’s Software Strategies
- Software Practices Compared to Tech Giants
- Key Takeaways and Future Challenges
Listen to it here on Spotify:
About Our Spotify Podcast Series
Ready for a brain boost that fits right into your coffee break? Then dive headfirst into Deep Dives with Jane and Austin! Our AI hosts, Jane and Austin, discuss management topics from angles you might not have even considered. Think short, sharp, and packed with fresh perspectives – perfect for sparking new ideas on your commute or shaking up your afternoon slump.
Deep Dives with Jane and Austin are carefully crafted using advanced AI technology. They draw from my talks, writings, and teaching materials from my classes at TH Rosenheim plus hand-curated content from expert sources.
Do you have a burning management question or a topic you’re eager to see explored? We’d love to hear about it: janeandaustin@go3consulting.com