News
Tesla’s race to autonomy: No one said it would be easy
Need to type up a quick memo before work? Forgot to eat breakfast before driving to school? In just a few years, driving may be a more hands-off endeavor than ever before if companies like Tesla, Uber, Volvo, Alphabet, General Motors, or Ford have anything to do about it. You could be a passenger in your own self-driving car, weaving in and out of traffic with ease and parallel parking like a pro every time. It seems like most every company even tangentially related to cars is pouring money into the race for autonomy.
The freedom of self-driving cars is still heavily dependent on regulatory whim and technological availability, but some are setting demanding goals in an effort to finish first in that race. Tesla for example, plans to showcase its Full Self-Driving Capability by driving one of its fleet cars from California to New York, without human involvement, by the end of this year. But their competitors are moneyed, motivated and many.
The Self-Driving Battle Arena
For Uber, success in autonomous driving research could be a sweet distraction from the recent troubles of the company. Its self-driving program has been based in Pittsburgh, right next to Carnegie Mellon with its highly regarded robotics program since it began in 2015. Then-CEO Travis Kalanick was determined to stay on top of the industry. “It starts with understand that the world is going to go self-driving and autonomous,” Kalanick said in a 2016 interview with Business Insider. “So if that’s happening, what would happen if we weren’t a part of that future? If we weren’t part of the autonomy thing? Then the future passes us by basically, in a very expeditious and efficient way.”
Plagued by lawsuits, investigations, and subsequent executive upheaval that saw Kalanick’s resignation from the enterprise he founded, Uber is still one of the best places for researchers and engineers to work on their projects. The company has armies of vehicles across the country, vast datasets of information from the millions of miles its cars have covered through its ride-hailing branch, and the money to fund its engineers’ work.
This does not mean that Uber’s self-driving program has remained untouched. Waymo, the autonomous car division of Google’s parent company, Alphabet, is currently suing Uber over files allegedly by Anthony Levandowski when he moved from Waymo to Uber. According to Reuters, in recent court filings, Waymo has claimed that Uber knew of the stolen intellectual property and even conspired with Levandowski to use it. Uber denies the allegations and actually fired Levandowski on May 30, claiming he had not cooperated with their internal investigation– and probably hoping to win some goodwill from the judge who has already said Waymo had produced a convincing case.
It is unlikely the scandals will affect the decisions of most researchers to stay with the company. As Wired’s Aarian Marshall points out, the long timeline of building a safe autonomous car makes engineers less likely to leave at a moment’s notice in a period of executive instability. And the branch’s position in Pittsburgh rather than Silicon Valley means the roiling news is less sensationalized and the researchers less affected. The ride-sharing company’s failure to live up to certain promises, including backing one of Pittsburgh’s federal grant proposals or hiring from neighborhoods near its test tracks, have drawn ire from many local activists and politicians, as reported by the New York Times. Even so, it has helped the city break away from its steel past and into a high-tech future.
Meanwhile, Uber’s main competitor in the ride-sharing industry, Lyft, has been making strides to continue chipping away Uber’s monopoly in any field, including self-driving cars, as Uber deals with scandal after scandal. As reported by Recode, Lyft is steadily gaining ground on Uber in terms of the share of ride-hailing app downloads as its ratings in the IOS App Store rise and Uber’s falls. This recent shift in market share comes as Waymo and Lyft start a new partnership that will combine Waymo’s advanced technology with Lyft’s vast amounts of data on people, where and how they drive. “Lyft’s vision and commitment to improving the ways cities move with help Waymo’s self-driving technology reach more people, in more places,” a Waymo spokesperson told Wired. Extending Waymo’s dataset beyond the few cities, including Phoenix and Pittsburgh, allows the enterprise to collect the small details of average people’s driving habits much faster and accurately than its test drives around Silicon Valley will.
But despite Waymo’s eight years of self-driving research, it still has to play catch up to Uber in some regards. Waymo just started testing autonomous trucks earlier this month, while Uber first used a self-driving truck to deliver a shipment last August, advancing its technology quickly after it snatched up the self-driving truck startup Otto—founded by Anthony Levandowski after he left Waymo— in January of 2016. Yet, Waymo has the benefit of its parent company’s huge cash reserves and data.
Growing Pains
Tesla is moving its autonomous program forward at an increasingly demanding pace, trying to meet that goal of driving from Los Angeles to New York by the end of this year. It, like Uber, is going through some executive shakeup: after just six months with Tesla, Chris Lattner, Vice President of its Autopilot Software program, left the company after reported tensions with Elon Musk. Tesla explained that the former Apple engineer was not a “good fit.” It stands to mention that working under Musk is notoriously a high-pressure gig. According to LinkedIn Insights, the average tenure of a Tesla employee is only 2.2 years, while companies like General Motors keeps its employees for almost 9. But Lattner’s exit is just one example of many of talented Tesla self-driving engineers leaving the company or being poached by the competition, like Waymo.
While Autopilot can do many impressive things— change lanes, brake before obstacles, and generally act as a rational human driver— it is far from perfect. The program is still technically in “public beta” testing, and rated by the National Transportation Safety Board as a 2 out of 5 on its scale of autonomy.
The fatal crash of a Model S owner Joshua Brown in May 2016 serves as a good reminder that drivers are cautioned to pay attention and keep their hands on the wheel at all times while using Autopilot. Tesla’s driving-assist feature, at the time, could not distinguish the difference between the bright sky and the white truck. Tesla and Autopilot were cleared of responsibility by the NTSB because Brown was given several warnings to take back control of the wheel. But it is a poignant example that Autopilot does not function as a self-driving car and still requires a driver’s full attention. After the accident, Tesla was forced to start developing its own hardware for Autopilot. Mobileye, which previously supplied Tesla’s image processing chips, ended its partnership in a public spat with Musk.
According to Lattner’s public resume, the transition to its own hardware presented “many tough challenges” to the Tesla team. Musk commented to shareholders in June that Tesla is “almost there in terms of exceeding the ability” of the original hardware. All of Tesla’s vehicles in production, including the upcoming Model 3, have the capability to engage Autopilot (for a price) and the necessary hardware to enable full self-driving someday. Autopilot will continue using the camera-based system that Tesla swears by, even as most of the industry focuses on developing LiDAR technology based on light and lasers.
And while Tesla prefers to work mostly alone, the rest of the industry is also pairing up, making deals, partnerships, and contracts between manufacturers, data giants, and service teams. Musk is taking a move out of Steve Jobs’ playbook by vertically integrating everything within the business, from top-to-bottom. Waymo and Honda, Lyft and Waymo, Autoliv and Volvo, Hertz and Apple, Intel and Mobileye, Audi and NVIDIA, and almost every other combination you could think of. Predictions for when the first company will reach the finish line range from within a year to two decades from now. And even if the car is made, there is still the question of if cities and states will allow autonomous vehicles to drive on their streets. The technology is closer than ever, but for now, please keep your eyes on the road.
Elon Musk
Tesla CEO Elon Musk teases insane capabilities of next major FSD update
Tesla CEO Elon Musk teased the insane capabilities of the next major Full Self-Driving update just hours after the company rolled out version 14.2 to owners.
Tesla Full Self-Driving v14.2 had some major improvements from the previous iteration of v14.1.x. We were on v14.1.7, the most advanced configuration of the v14.1 family, before Tesla transitioned us and others to v14.2.
However, Musk has said that the improvements coming in the next major update, which will be v14.3, will be where “the last big piece of the puzzle finally lands.”
14.3 is where the last big piece of the puzzle finally lands
— Elon Musk (@elonmusk) November 21, 2025
There were some major improvements with v14.2, most notably, Tesla seemed to narrow in on the triggers that caused issues with hesitation and brake stabbing in v14.1.x.
One of the most discussed issues with the past rollout was that of brake stabbing, where the vehicle would contemplate proceeding with a route as traffic was coming from other directions.
We experienced it most frequently at intersections, especially four-way stop signs.
Elon Musk hints at when Tesla can fix this FSD complaint with v14
In our review of it yesterday, it was evident that this issue had been resolved, at least to the extent that we had no issues with it in a 62-minute drive, which you can watch here.
Some owners also reported a more relaxed driver monitoring system, which is something Tesla said it was working on as it hopes to allow drivers to text during operation in the coming months. We did not test this, as laws in Pennsylvania prohibit the use of phones at any time due to the new Paul Miller’s Law, which took effect earlier this year.
However, the improvements indicate that Tesla is certainly headed toward a much more sentient FSD experience, so much so that Musk’s language seems to be more indicative of a more relaxed experience in terms of overall supervision from the driver, especially with v14.3.
Musk did not release or discuss a definitive timeline for the release of v14.3, especially as v14.2 just rolled out to Early Access Program (EAP) members yesterday. However, v14.1 rolled out to Tesla owners just a few weeks ago in late 2025. There is the potential that v14.3 could be part of the coming Holiday Update, or potentially in a release of its own before the New Year.
News
Tesla Full Self-Driving v14.2 – Full Review, the Good and the Bad
Tesla rolled out Full Self-Driving version 14.2 yesterday to members of the Early Access Program (EAP). Expectations were high, and Tesla surely delivered.
With the rollout of Tesla FSD v14.2, there were major benchmarks for improvement from the v14.1 suite, which spanned across seven improvements. Our final experience with v14.1 was with v14.1.7, and to be honest, things were good, but it felt like there were a handful of regressions from previous iterations.
While there were improvements in brake stabbing and hesitation, we did experience a few small interventions related to navigation and just overall performance. It was nothing major; there were no critical takeovers that required any major publicity, as they were more or less subjective things that I was not particularly comfortable with. Other drivers might have been more relaxed.
With v14.2 hitting our cars yesterday, there were a handful of things we truly noticed in terms of improvement, most notably the lack of brake stabbing and hesitation, a major complaint with v14.1.x.
However, in a 62-minute drive that was fully recorded, there were a lot of positives, and only one true complaint, which was something we haven’t had issues with in the past.
The Good
Lack of Brake Stabbing and Hesitation
Perhaps the most notable and publicized issue with v14.1.x was the presence of brake stabbing and hesitation. Arriving at intersections was particularly nerve-racking on the previous version simply because of this. At four-way stops, the car would not be assertive enough to take its turn, especially when other vehicles at the same intersection would inch forward or start to move.
This was a major problem.
However, there were no instances of this yesterday on our lengthy drive. It was much more assertive when arriving at these types of scenarios, but was also more patient when FSD knew it was not the car’s turn to proceed.
Can report on v14.2 today there were ZERO instances of break stabbing or hesitation at intersections today
It was a significant improvement from v14.1.x
— TESLARATI (@Teslarati) November 21, 2025
This improvement was the most noticeable throughout the drive, along with fixes in overall smoothness.
Speed Profiles Seem to Be More Reasonable
There were a handful of FSD v14 users who felt as if the loss of a Max Speed setting was a negative. However, these complaints will, in our opinion, begin to subside, especially as things have seemed to be refined quite nicely with v14.2.
Freeway driving is where this is especially noticeable. If it’s traveling too slow, just switch to a faster profile. If it’s too fast, switch to a slower profile. However, the speeds seem to be much more defined with each Speed Profile, which is something that I really find to be a huge advantage. Previously, you could tell the difference in speeds, but not in driving styles. At times, Standard felt a lot like Hurry. Now, you can clearly tell the difference between the two.
It seems as if Tesla made a goal that drivers should be able to tell which Speed Profile is active if it was not shown on the screen. With v14.1.x, this was not necessarily something that could be done. With v14.2, if someone tested me on which Speed Profile was being used, I’m fairly certain I could pick each one.
Better Overall Operation
I felt, at times, especially with v14.1.7, there were some jerky movements. Nothing that was super alarming, but there were times when things just felt a little more finicky than others.
v14.2 feels much smoother overall, with really great decision-making, lane changes that feel second nature, and a great speed of travel. It was a very comfortable ride.
The Bad
Parking
It feels as if there was a slight regression in parking quality, as both times v14.2 pulled into parking spots, I would have felt compelled to adjust manually if I were staying at my destinations. For the sake of testing, at my first destination, I arrived, allowed the car to park, and then left. At the tail-end of testing, I walked inside the store that FSD v14.2 drove me to, so I had to adjust the parking manually.
This was pretty disappointing. Apart from parking at Superchargers, which is always flawless, parking performance is something that needs some attention. The release notes for v14.2. state that parking spot selection and parking quality will improve with future versions.
Any issues with parking on your end? 14.1.7 didn’t have this trouble with parking pic.twitter.com/JPLRO2obUj
— TESLARATI (@Teslarati) November 21, 2025
However, this was truly my only complaint about v14.2.
You can check out our full 62-minute ride-along below:
Elon Musk
SpaceX issues statement on Starship V3 Booster 18 anomaly
The incident unfolded during gas-system pressure testing at the company’s Massey facility in Starbase, Texas.
SpaceX has issued an initial statement about Starship Booster 18’s anomaly early Friday. The incident unfolded during gas-system pressure testing at the company’s Massey facility in Starbase, Texas.
SpaceX’s initial comment
As per SpaceX in a post on its official account on social media platform X, Booster 18 was undergoing gas system pressure tests when the anomaly happened. Despite the nature of the incident, the company emphasized that no propellant was loaded, no engines were installed, and personnel were kept at a safe distance from the booster, resulting in zero injuries.
“Booster 18 suffered an anomaly during gas system pressure testing that we were conducting in advance of structural proof testing. No propellant was on the vehicle, and engines were not yet installed. The teams need time to investigate before we are confident of the cause. No one was injured as we maintain a safe distance for personnel during this type of testing. The site remains clear and we are working plans to safely reenter the site,” SpaceX wrote in its post on X.
Incident and aftermath
Livestream footage from LabPadre showed Booster 18’s lower half crumpling around the liquid oxygen tank area at approximately 4:04 a.m. CT. Subsequent images posted by on-site observers revealed extensive deformation across the booster’s lower structure. Needless to say, spaceflight observers have noted that Booster 18 would likely be a complete loss due to its anomaly.
Booster 18 had rolled out only a day earlier and was one of the first vehicles in the Starship V3 program. The V3 series incorporates structural reinforcements and reliability upgrades intended to prepare Starship for rapid-reuse testing and eventual tower-catch operations. Elon Musk has been optimistic about Starship V3, previously noting on X that the spacecraft might be able to complete initial missions to Mars.


