#364: Alex Got Solar, Uber’s AV Future, Waymo Ops, Gossip, Ed’s Fave Robotaxis

Morgan is a British car brand best known for producing small-run, traditional-style sports cars. In this segment, it’s mentioned as a consumer-shopping example (“you bought a Morgan”), not as a technical discussion of the vehicle.

EV stands for electric vehicle, meaning a car powered by an electric motor and charged from an external power source. The hosts connect EV charging habits to whether home solar makes financial sense.

Net metering is a utility billing arrangement where excess electricity your solar panels produce can be credited against the electricity you draw from the grid. The hosts mention it because it strongly affects whether solar “pencils out” financially for a homeowner.

Weatherization refers to home improvements that reduce heat loss and drafts—like sealing gaps, insulating, and upgrading building envelope details. The host contrasts providers that only sell solar panels with those that also do weatherization, arguing that overall energy efficiency is a system-level problem.

“Vertical integration” means one company controls multiple steps of a product or service chain, from hardware to installation and related services. Here, the host argues Tesla’s solar push is framed as a vertically integrated home energy ecosystem that could include solar plus other upgrades that reduce energy use.

The “SolarCity deal” in 2016 refers to the financial and corporate transaction involving SolarCity, which was closely associated with Elon Musk and Tesla’s broader energy strategy. The host frames it as potentially being a bailout of a failing company, and uses it to question the motivations behind Tesla’s solar expansion.

A battery storage system stores electricity generated by solar panels so it can be used later, such as at night or during outages. In residential solar setups, pairing panels with storage is often what makes the system more “comprehensive” rather than just producing daytime power.

“Driverless product” refers to a robotaxi or autonomous service that can operate without a human driver taking over. In practice, it usually depends on limited operating conditions (like specific areas and mapping) and can still struggle with edge cases.

Austin is the Texas city where Tesla’s robotaxi demonstrations and operations are being discussed. The hosts use it as the real-world test location for evaluating wait times, pickup/drop-off behavior, and turn-handling.

A robot taxi is an autonomous ride-hailing service where the vehicle drives itself to pick up and drop off passengers. The segment highlights that operational issues—like long waits—can make the experience worse than a human-driven ride.

ODD stands for “Operational Design Domain,” meaning the specific set of conditions under which an autonomous system is designed to work. Wait times can be affected by how many vehicles are available relative to the size/complexity of the ODD.

In autonomous ride-hailing, “pickups and drop-offs” refer to where the system will actually stop to let passengers get in and out. The transcript notes that these can be far from the exact location marked in the app, which is a practical limitation of real-world autonomy.

A “left-hand turn” is a common autonomy stress test because it requires judging oncoming traffic gaps, crosswalks, and complex right-of-way rules. The segment claims Tesla was struggling or refusing left turns and instead making a sequence of right turns to reach the same destination.

ETAs are “Estimated Times of Arrival.” In robotaxi operations, ETAs are a key customer-facing metric that depends on fleet size, dispatching, and how often vehicles are available near pickup points.

Tesla is referenced in the context of autonomous-driving strategy—specifically whether it will aim for “mass ubiquity” with a strong user experience sooner, or take a slower approach to maintain momentum. The discussion frames Tesla as a benchmark for how AV companies communicate progress.

Robotoxytracker is discussed as a tool for monitoring robotaxi operations—especially metrics tied to rider vehicles, pickup performance, and delay causes. The hosts treat it as an example of how data visibility can improve service quality.

Argo is mentioned as having built internal tools for robotaxi operations, including tracking ETAs and diagnosing delay causes. The host uses it to illustrate that data-driven operations are a common need across AV companies.

“Unsupervised” refers to robotaxi operations where the vehicle can drive without a human safety driver actively monitoring the system in real time. It’s a major milestone because it implies higher autonomy and different operational risk controls.

Houston is cited as a robotaxi market with a stated number of rider vehicles. It’s part of a city-by-city breakdown of fleet size and autonomy level.

Dallas is mentioned as another robotaxi market with a specific number of rider vehicles. The host uses these figures to compare operational scale across cities.

Bay Area is referenced as a robotaxi region with a much larger fleet count than the other markets mentioned. The host also notes that none of those vehicles are using unsupervised operation, highlighting a difference in autonomy readiness.

FSD stands for “Full Self-Driving,” Tesla’s driver-assistance software package aimed at automating more of the driving task. In this context, the hosts are discussing how “FSD” is still being driven/managed by a human contractor rather than being fully autonomous.

Lyft is mentioned alongside Uber as part of the pricing comparison for robotaxi services. The hosts are arguing that riders may choose the cheaper option regardless of the “innovation” narrative.

Waymo is the autonomous-driving company whose robotaxi operations are used as the benchmark in this discussion. The hosts talk about Waymo expanding its ODD and also note operational issues like empty vehicles showing up in neighborhoods.

“Narrative command” is a rhetorical idea: whoever controls the story about performance (like “fastest growing AV operator”) can shape public perception even if the underlying operational metrics are messy. The hosts contrast it with other ways of framing the same situation.

“Thought terminating” refers to language or messaging that shuts down further scrutiny—essentially preventing people from digging into inconvenient details. In the segment, the hosts use it to criticize how AV operators may frame growth claims to avoid discussing operational shortcomings.

San Francisco is used as an example location where Waymo robotaxis have been observed behaving oddly—specifically, “empty” vehicles appearing in neighborhoods. The hosts later mention the same kind of issue in Atlanta, implying it’s not isolated.

A robotaxi is a self-driving taxi service where the vehicle performs the driving task without a human driver in the car. The key challenge is handling unpredictable real-world situations—like moving objects or unusual road conditions—while keeping incident rates low.

Atlanta is referenced as one of the cities where Waymo robotaxis were observed waiting/queuing in a neighborhood setting. The point is to show how operational behaviors can repeat across deployments.

A recall process is the formal procedure manufacturers use to address a safety-related problem, often involving software updates or hardware fixes. In autonomous fleets, recalls can be triggered by issues discovered after deployment, then rolled out across the entire fleet to reduce risk.

A software update is a change to the vehicle’s onboard code—such as perception, planning, or behavior logic—that can improve how it drives or handles hazards. For autonomous systems, updates can be safety-critical because they alter how the car interprets and reacts to the environment.

Flooded areas are a hazardous driving condition where water can obscure road boundaries, depth, and traction, making it hard for autonomous systems to judge what’s safe. The hosts describe a Waymo fleet update aimed at improving the vehicles’ ability to detect and navigate around flooding.

San Antonio is referenced in connection with flooding that affected a Waymo vehicle and delayed a planned launch. The hosts use this example to distinguish operational annoyances from safety-related incidents.

“Wayma” appears to refer to Waymo, the autonomous-vehicle company known for operating self-driving cars in public areas. The segment discusses Waymo’s recurring challenges when expanding to new cities and how incidents like flooding raise insurance and write-off questions.

A “write-off” means the insurer determines the vehicle is too expensive to repair and treats it as a total loss. In autonomous-vehicle contexts, this becomes especially important because damage events (like flooding) raise questions about coverage, liability, and how the vehicle is recovered or replaced.

AV insurance is coverage tailored to autonomous-vehicle incidents, including questions like who is liable when the vehicle is operating on its automation stack. It also has to account for high-cost scenarios like vehicle damage from flooding and whether the vehicle is treated as a total loss (write-off).

“Cul-de-sac parade behavior” describes a recurring autonomous-driving failure mode where the vehicle behaves in a socially awkward or inefficient way in dead-end streets—often involving repeated slow maneuvers, waiting, or looping patterns. It’s an operations/behavior-planning issue that shows up when the system can’t confidently interpret the environment or choose a safe maneuver.

In autonomous vehicles, “system design” is building the driving stack (sensing, perception, planning, control) to meet requirements, while “validation” is proving it works through testing—often including edge cases. The discussion highlights that it can be blurry where engineering/testing ends and real-world operations begin when failures repeat in new cities.

“L4” is the SAE autonomy level for highly automated driving. At L4, the car can handle most driving tasks in specific conditions/areas without a human constantly supervising, but it may still require human help outside its designed “geofenced” domain.

In AV discussions, “sensors” refers to the hardware used to perceive the world—commonly cameras, radar, and lidar. The transcript contrasts “experience and sensors and operations” with the idea that another company (Tesla) can avoid the same real-world challenges.

“Self-driving” refers to an autonomous driving system that handles driving tasks without a human actively controlling the vehicle. In the segment, it’s framed as a resource-intensive problem that companies must keep iterating through multiple development and deployment phases.

AV Ride is discussed as an autonomous-vehicle operation that originated as part of Yandex and later changed due to the Ukraine war. The segment also ties AV Ride to real-world robotaxi/safety scrutiny and crash investigations involving its self-driving system.

Yandex is referenced as the original parent context for AV Ride. This matters because it explains why AV Ride’s operations and corporate structure shifted over time.

The Hyundai Ioniq 5 is an electric crossover that’s being used in the AV Ride robotaxi/self-driving context mentioned in the segment. The key point is that autonomous fleets often rely on specific EV models as the “robotaxi platform,” not just generic cars.

NHTSA (National Highway Traffic Safety Administration) is the U.S. federal agency that investigates vehicle safety issues and can open formal probes. In this segment, it’s used to describe regulatory scrutiny after multiple crashes involving an AV Ride self-driving system.

“Changing lanes” is a driving maneuver that autonomous systems must plan and execute safely while accounting for nearby traffic. The segment specifically claims AV Ride’s system struggled with lane changes, which is a common hard problem for robotaxis.

“Stationary objects” in autonomous driving refers to fixed things in the vehicle’s path—like parked cars, debris, or obstacles that don’t move. The segment uses this to describe a specific perception/planning weakness attributed to AV Ride’s self-driving system.

Motional is listed as one of the companies aiming to scale robotaxis/AV services by 2028. The segment groups it with other AV operators to emphasize how many players are working on the same deployment challenge.

“Moya” is likely a mis-transcription of Moia, a Volkswagen-affiliated mobility/robotaxi initiative. The segment pairs it with Uber, suggesting a partnership-driven approach to scaling autonomous mobility services.

Mobileye is mentioned as part of the AV ecosystem expected to scale by 2028. Mobileye is known for driver-assistance and autonomy-related technologies, so its inclusion signals the role of sensing/compute platforms in robotaxi development.

The Rivian R2 is an electric vehicle from Rivian, discussed here in the context of robotaxis—autonomous rideshare vehicles. The podcast is highlighting the idea that large fleets of R2-based autonomous vehicles could be deployed, which is significant because it ties the car to real-world self-driving operations rather than just consumer use.

“AV” stands for autonomous vehicle—cars or shuttles that use sensors and software to drive without a human driver controlling the vehicle. In this context, it’s about the broader challenge of making autonomous tech work for real riders, not just in demos.

Uber is a ride-hailing company that’s also pursuing autonomous vehicle (AV) technology. In this segment, the host discusses Uber’s quarterly call messaging about how AVs should work with regulators and in real-world edge cases like power outages and school zones.

“Dara” refers to Dara Khosrowshahi, Uber’s CEO at the time of the discussion. The segment highlights his comments about engaging regulators and framing AV behavior questions—implicitly contrasting Uber’s approach with Waymo’s incidents and operational scenarios.

“Robotoxies” is a slangy reference to robotaxis—autonomous vehicles operating as on-demand taxis without a human driver. The host uses it in the context of regulations and how AVs should behave in public settings like school zones and during emergencies.

In AV operations, “power goes out” refers to scenarios where the vehicle’s systems or supporting infrastructure lose power, potentially causing a shutdown or requiring fallback behavior. The host claims this is a uniquely discussed Waymo scenario where vehicles were “locked down,” and first responders had to intervene.

“School zones” are a high-risk driving environment for AVs because of unpredictable pedestrian behavior, crossing patterns, and strict speed/behavior expectations. The host frames this as a specific operational context where Waymo’s behavior has been discussed in the context of regulatory scrutiny.

“First responders” are emergency personnel (like firefighters and paramedics) who take over during incidents. The host claims there have been reports that first responders sometimes have to jump in and drive Waymo vehicles when the AV can’t safely continue on its own.

Travis Kalanick is a co-founder and former CEO of Uber. The host uses his name to reference Uber’s earlier strategy—pushing for an in-house autonomous solution—contrasting it with Uber’s more recent “fast followers” posture.

“Autonomous solution in-house” means building the self-driving stack internally rather than relying on partners or a “fast followers” strategy. The host suggests that regulatory tension with Waymo could push Uber back toward developing its own AV technology directly.

A “fast followers approach” is a strategy where a company moves quickly to adopt or refine proven ideas after others have already validated them. In the segment, the host contrasts Uber’s earlier in-house AV push with a strategy of following what leading AV operators (like Waymo) are doing first.

In autonomous mobility, a “hybrid model” usually means the service still relies on humans in some role (for example, remote assistance or human supervision) rather than being fully driverless. The hosts contrast Uber’s “hybrid” approach with Waymo’s more fully autonomous strategy, arguing that this affects risk and scalability.

“AV Kremlinology” is a playful term for trying to infer what autonomous-vehicle companies are really doing (and what their next moves might be) from partial signals like strategy statements, partnerships, and market behavior. In this segment, it’s used to frame the debate about Uber’s hedging versus Waymo’s all-in approach.