Pinned Tweet
‼️ Cardinals Fans ‼️
Thanks to everyone who filled out the Fan Survey!
Here's an update on what's happening now and a few of my thoughts as well.
Dear Mr. Anderson,
Tesla never ignored physics.
I'm writing because of what you told The Verge on October 27, when you called dropping radar from a self-driving car "a weird religious stance that ignores physics." That line got a lot of attention among Tesla owners, and I think it deserves a direct answer.
You know this territory better than most. You ran Tesla's Autopilot program from late 2015 to late 2016, cofounded Aurora, and now lead product at GM.
Your new employer is betting the other way. A 2028 Cadillac Escalade IQ will launch eyes-off highway driving with cameras, radar and lidar all working together.
As I understand it, your case rests on four claims. Lidar helps camera systems learn faster, cameras can't see through dense fog, cameras can't measure instantaneous velocity the way radar can, and radar is so cheap that removing it makes no sense.
I agree that physics is real, and nobody at Tesla is pretending otherwise. What I'd like to show you is that Tesla's own engineering has been answering these exact points for years, and two of your arguments describe things Tesla already does.
A lot has also changed since you left. The in-house FSD computer arrived in 2019, camera-only Tesla Vision followed in 2021, and the end-to-end neural network that drives the car today came in 2024.
So let me take your physics one claim at a time.
🎓 ON LIDAR AS A TEACHER, TESLA HAS BEEN DOING THAT FOR YEARS
You said lidar works on a wavelength close to visible light, so it helps camera systems learn faster. You're right, and Tesla agrees so strongly that it built an entire training pipeline around that idea.
I like to think of lidar as a tutor holding a perfect answer key. It measures distance directly by timing laser pulses, so it can grade every guess a camera network makes about how far away something is.
Tesla has designed a system where a special test fleet carries radar and lidar alongside the regular cameras. Every reading is synchronized, so the precise depth and speed from the expensive sensors get attached automatically to the objects the cameras see.
The labeling even uses hindsight. When two cars blur into one blob early in a clip and separate later, the training servers rewind the footage and use the clear moment to label the confusing one correctly.
Tesla applies the same teacher to 3D space itself. Its occupancy network learns from lidar-backed ground truth to predict, for every small cube of space around the car, how far that cube sits from the nearest surface.
That's how plain cameras learn to sketch a sloped curb or a curved bumper smoothly instead of as a pile of blocky Lego bricks.
Even the grading got faster. Tesla designed a cross-labeling trick that draws a box around a car in a flat photo, then projects that box into the laser point cloud as a pyramid of vision, so the software only searches that slice instead of the whole 3D world.
You probably know DeepScale, the startup Tesla acquired in 2019. It was already working out in 2016 how to train cheap sensors to mimic premium lidar data, and Tesla is still pursuing that work today.
Here's the step where our views split.
Once the student has learned, the teacher can stay home. The test fleet keeps the expensive hardware, and the cars customers actually buy ship with cameras only.
Tesla has put real money behind this. In early 2024, lidar maker Luminar named Tesla its largest customer for the quarter, and Elon soon replied on X, "We don't need them even for that anymore."
The student is even learning to write its own answer key. To map the shape of the road surface, Tesla has designed a method that can triangulate ground truth points straight from camera images instead of relying on lidar.
Co-training requires lidar in the classroom, not in every car on the road. With respect, GM's plan keeps the teacher riding along forever.
⚡ ON SPEED, CAMERAS ARE QUICKER THAN THEY LOOK
Your sharpest point is about speed. Radar can measure how fast something is moving in a single snapshot, and a camera can't.
Radar's trick is the Doppler effect, the same physics that makes an ambulance siren sound higher as it rushes toward you and lower as it drives away. Radar reads that pitch shift in its own radio echo to measure closing speed instantly.
A camera has to work speed out from motion. It compares where an object sits in one frame with where it sits in the next, much like you judge a thrown ball by watching it fly.
That sounds slower, but the gap is tiny. Tesla's own designs describe cameras running at rates such as 36 frames per second, which puts a fresh frame in front of the network about every 28 milliseconds, quicker than a single blink.
The physics also cuts both ways. Doppler only measures motion toward or away from the sensor, so a car crossing your path sideways at an intersection produces little to no Doppler shift.
To catch that sideways motion, a radar has to track the car across several scans, which is exactly what a camera does with frames. On that kind of motion, the "instantaneous" advantage disappears.
Radar has another well-known weak spot. Owner's manuals for radar-based cruise control have long warned that the system may not brake for a stopped vehicle, partly because a parked car, an overhead sign and a bridge can all look like the same motionless metal.
Now here's what Tesla has built since you left.
Tesla has designed its vision network to output a full 3D velocity vector for every object, covering speed, direction and even height. It learned that skill from the radar on its test fleet, which turns ordinary cameras into something that behaves like a Doppler radar made of pixels.
Tesla's virtual camera invention goes further by measuring speed in two different ways. Cars are tracked relative to the moving Tesla itself, while pedestrians are tracked against the fixed ground, so the system knows a person's true walking path even while the car accelerates or turns.
When things get fast, the network speeds up its memory. A frame selector pulls video snapshots more rapidly as speeds rise and blends them with the car's own acceleration and yaw rate, which is how quickly the car is rotating, to build a smooth picture of motion over time.
There's also a dedicated sentinel for the car directly ahead. A super-narrow model watches only the closest vehicle in the lane through the narrowest forward lens and keeps estimating its distance, speed and acceleration, which is exactly what you need to brake hard and early.
So yes, a camera infers velocity instead of measuring it in one shot. But inference refreshed every few dozen milliseconds, trained on radar's own answers, and able to see sideways motion that Doppler misses is not a camera ignoring physics.
🌫️ ON FOG, I'LL GIVE YOU THAT ONE, BUT HEAR ME OUT
No camera sees through dense fog, and neither does the human eye. Radar does.
But look closely at your own argument. The near-visible wavelength that you said makes lidar a great teacher is the same reason lidar struggles in fog, because the tiny water droplets that scatter visible light also scatter laser light.
So the fog argument is really a radar argument, and radar alone can't finish the job. It can't read lane paint, a traffic light, a speed limit sign or a flagger's hand signal, so even a car loaded with radar still leans on its cameras when the world turns gray.
That's why I think the real question isn't whether a car can see through fog. The real question is whether the car knows when its vision is degraded, and whether it behaves like a careful driver when it is.
This is where Tesla's visibility invention comes in.
Tesla has designed a separate neural network whose only job is grading its own eyesight. It splits every camera feed into a fine grid and scores each cell from clear to blacked out, building a live heat map of where the car can and can't trust what it sees.
Each camera position gets its own specialist. A model judging the left pillar camera was trained on images from that same pillar location across many other cars, because a windshield camera behind wipers and a fender camera facing tire spray get dirty in very different ways.
The system also diagnoses the cause. It can tell a smear of mud from fog, heavy snow or a hardware fault, then reach for the right fix, such as running the wipers or warming the glass.
When a lens is blinded for a moment, the car doesn't forget the road. Tesla anchors what it saw to fixed spots in the physical world, so a pothole hidden by a truck's spray stays pinned on the car's mental map for those few seconds.
And when conditions really are too much, the car responds the way a good human driver would. It slows down to widen its reaction window, can move to a safer lane, and can hand control back with a plain explanation such as "Due to Heavy Snow, Autopilot is Reducing Speed."
Tesla is also sharpening the eyes themselves. Its designs feed raw, unprocessed sensor data straight into the AI chip, the same idea behind the "photon count" images Elon posted in May, when he said this is why FSD can see so well at night or through extreme glare.
Around the lens, Tesla has designed micro-cone glare shields, corrective windshield patches, pulsed laser cleaning and even gas-absorbing plastics that keep a hazy chemical film off the inside of the glass. Each one attacks a different way a camera can lose its view.
Fog will always be fog. Tesla's bet is a car that measures how blind it is, remembers what it saw, and slows down exactly when a wise driver would.
💸 YES, RADAR IS CHEAP, BUT THAT WAS NEVER THE POINT
You're right that a radar unit doesn't cost much. But Elon's case against it was never about the sticker price.
In April 2021, as Tesla prepared to remove radar, Elon explained it this way: "Sensors are a bitstream and cameras have several orders of magnitude more bits/sec than radar (or lidar)." A second sensor, he added, has to meaningfully improve the signal to be worth the complexity of integrating it.
In August 2025 he put it even more bluntly: "Lidar and radar reduce safety due to sensor contention. If lidars/radars disagree with cameras, which one wins?" In the same post, he wrote that Tesla turned off the radars in its cars to increase safety.
Picture two witnesses to the same moment telling different stories. The radar reports a solid object ahead, the cameras see an empty road under a steel overpass, and the car has a fraction of a second to decide who's wrong.
Trust the radar every time and you get phantom braking under bridges. Trust the cameras every time and the radar was only along for the ride.
Then there's the cost that never shows up on a parts list. Every extra sensor needs calibration, its own data pipeline, fusion software and validation for every way the sensors can disagree, and that burden grows with each new sensor type.
Tesla's own history shows how heavy that lift is. The DeepScale design for mimicking lidar needed separate neural branches for each sensor type just to absorb their different quirks, timing and mounting positions before merging them.
I'd argue the biggest hidden cost is data. Tesla's FSD (Supervised) fleet has logged more than 16.7 billion miles, nearly all of it seen through cameras alone, and a radar channel added today would arrive with none of that history to learn from.
Look at what happened at Volvo this summer. In July, the company confirmed it was dropping lidar from the EX90 and ES90 after cutting ties with its supplier Luminar, which went bankrupt, and Norwegian owners are receiving NOK 18,000 per car for lidar features that never arrived.
Elon's reply was short: "I did try to warn them. Humans drive using neural nets and optical sensors. Same is true for robot cars."
Cheap hardware can turn into an expensive argument, and back in 2021 Tesla decided it would rather not have the argument at all.
🛣️ WHILE YOUR SYSTEM WAITS FOR 2028, CAMERA-ONLY TESLAS ARE ALREADY LOGGING THE MILES
Your plan for handing control back deserves real credit. You said the Escalade won't toss the wheel to a surprised driver, and will instead give a countdown of around ten minutes and pull off at an exit if nobody takes over.
That philosophy should sound familiar, because Tesla's visibility invention describes the same graceful exit. The car slows down first, looks for a safer lane, explains the reason on the screen, and only then hands control back.
The real difference is timing. GM's eyes-off system is still a 2028 promise, while Tesla's camera-only cars are collecting evidence right now.
Tesla's latest FSD (Supervised) safety report shows 6,006,200 miles per major collision in North America, compared with a U.S. average of 660,164 miles. That's roughly nine times as far between airbag-level crashes, measured over a rolling twelve months.
Tesla's new Robotaxi safety report goes a step further. Driverless Teslas with no safety monitor inside have covered 3.1 million miles in Texas and Florida this year, including 862,000 miles after dark and 113,000 miles in rain, with zero people injured by a Robotaxi and zero airbag deployments, based on the crash reports Tesla files with NHTSA.
And that Robotaxi fleet runs on the latest Model Y and the Cybercab, neither of which carries radar or lidar. I find that hard to square with the idea that camera-only driving ignores physics.
🔭 WHERE I THINK WE REALLY DISAGREE
You framed this as physics versus faith, but I think both sides accept the same physics. What we really disagree about is where the intelligence should live.
GM puts more of it in the hardware, stacking sensors so each one covers another's weak spot. Tesla puts it in the neural network, using radar and lidar as teachers in the classroom and then trusting a trained brain behind the cameras.
There's a quiet twist hidden in that choice. A multi-sensor car can only learn from fleets that carry the same sensors, while every camera-equipped Tesla on the road feeds the same classroom.
Physics decides what a sensor can see. Data decides what a car understands.
Best regards,
Ming
P.S. If you're ever in Austin, a driverless Tesla might make my case better than I can, and it won't need lidar to find you.
Thanks again to @MrAzSports and @LieuSandi for the collaboration on the survey!
You can view the results here:
cardinalssurvey.com
Christopher Maddox retweeted
The Inside The NBA crew reacts to Ernie Johnson announcing this will be his last season on the show ❤️
Christopher Maddox retweeted
JUST IN: Neuralink announces breakthrough in restoring speech for ALS patients, reporting that its brain implants can now convert neural signals into text & voice at conversational speeds.
Christopher Maddox retweeted
Big Cat is on the warpath against Arizona Cardinals owner Michael Bidwill and lists some of the shitty things he has done as owner over the years:
It’s either growing pains, or, a lot of fans were right about fit concerns.
The real question is how long do they roll with it and are Suns brass giving Ott the freedom to make that call?
Christopher Maddox retweeted
Quietly one of the most horrific trades you'll see...
2033 UNPROTECTED for Miles Bridges and a fake first
Not to mention Grayson Allen currently averaging 17 PPG on 74.6 TS%. Just a really tough pill to swallow for a team that was already light on future assets. Sloppy FO work.
Christopher Maddox retweeted
The people on this platform I respect the most are those who constructively criticize their own tribe (or don't even have a tribe), are ruthlessly guided by a coherent set of principles, will acknowledge and accept facts that do not flatter their own positions or worldview, change their positions when facts warrant it, avoid hypocrisy (or at least acknowledge when they are engaging in it), and are capable of stripping away their own personal history and any moral arguments in order to inspect the logical or factual structure of an argument (i.e., cognitive decoupling).
But truth-seeking and intellectual honesty demand more than most people are willing to invest.
Christopher Maddox retweeted
I think it's pretty clear now, Mike LaFleur doesn't have the ability to make a changes that would improve the weekly performance of this football team.
You can't tell me a rookie HC who's worked his entire life to get to this point of his career, as a head coach for an NFL team, is content with doing the same thing week in and week out, knowing it won't change.
It's about the money.
The QB situation is pretty obvious.
The NFL average QB rating is 91.6. Brissett is 8 spots lower at 82.8; 25th overall. (He is higher than Kyler in QBR... for QBR guys 😅)
The difference?
Brissett has incentives that are still a ways off.
He's 14 TD's away from a $1.25M bonus and 2,000 yards away from another $1.4M bonus.
Minshew has play time incentives of $1.125M at 50% and $2.25M at 65%.
We're not to the halfway point in the season yet.
Next, take a look at the RB situation. Why are they splitting carries when it's clear Tyler Allgeier, for whatever reason, is struggling to run the ball?
On the season, he's averaging only 2.9 yards per carry.
Blame the offensive line all you want, but Bam Knight is averaging 6.4 ypc.
Knight has earned extra snaps/carries, but Allgeier is being paid $6.1M/year.
Now, coaching changes.
Under Nick Rallis, the team has finished 31st, 15th, 29th and is currently 32nd in points allowed. Their best rank in takeaways under Rallis has been 19th ('25 & '26).
In all 5 of their losses this year, the Cardinals allowed over 30 points.
Over the past 17 games, they've allowed over 30 or more 11 times.
Since hired, 24 of 58 games, 41.3%.
Rallis was retained for two main reasons. 1) those who interviewed for the position didn't want the job, and 2) Rallis would have still been owed his salary for the 2026 season. Coordinators make more ($1m-$3M) than position coaches ($300k-$700k). Translation: even with an offset, the Cardinals would have been paying another coach not to be here.
Since the departures of Keim and Kingsbury in early 2023, it's been pretty clear the organization has prioritized money over building a competitive team.
The bad news, the deals for Keim, Kliff, and Gannon don't expire until the end of the 2027 season.
Nailed it regarding Green and Bridges.
Quick notes on Oklahoma City Thunder-Phoenix Suns last night, which the Thunder controlled pretty comfortably. Also, a follow up tweet about future plans for these Game Notes.
-Shai is a dominant force. Just totally took over and got to all the spots he wanted. No issues, didn't feel rushed at all. When he got blitzed, he hit the short roll player consistently. When he got one-on-one matchups with Brooks, he attacked and just relentlessly got to that 8-to-14-foot area and buried jumpers. Typical Shai game. Brooks couldn't do anything with him. 26 points on 11-18 from the field in just 30 minutes because he dealt with foul trouble. Simple game, dominant game.
-Ajay Mitchell was terrific. Phoenix's defensive scheme against Oklahoma City's offensive plan of empty actions and angle screens just fed directly into what makes him so great. Phoenix just let Mitchell snake back to the middle on every screen it felt like, where he can just be utterly lethal. Hit a bevy of midrange shots early, then also started to get to the rim late when he got switches against Luke Kennard. Also liked some of the Iverson action they ran to get Mitchell downhill going toward his left. Ended up getting 10 free throws. Also played well on defense.
-The bigs also totally dominated the game for Oklahoma City, Both Hartenstein and Mara had double-doubles, and they went a combined 10 of 13 from the field. It felt like without Chet or JDub, Oklahoma City used a lot more Hartenstein hand-off action to initiate sets, especially when Shai was out or when they wanted to run him off of the ball to get a clean look. Nine offensive rebounds between the two of them and they totally controlled the paint defensively. Phoenix only had 38 points in the paint. Also thought Hartenstein was really good in short-rolls with Shai.
-Oklahoma City's defense was interesting. Thought that their aggression in blitzing Booker to get the ball out of his hands was really sharp, and they really did a great job making his life harder off of the ball. Even when he caught with one defender on him, their gap defense was spectacular. He only ended up with three points, which meant Phoenix was more reliant on Jalen Green to initiate. More on that later. Mitchell particularly made life very hard for Booker, getting into his chest and making his life hard. Just was a really physical presence. I will note that I thought their off-ball work was a little bit messier than normal. Jared McCain got back-cut twice ball-watching leading to easy dunks. They also went to a 2-3 zone more regularly than I've seen them do in a while. They've been experimenting with it in the early part of the season, but it felt like they went to it for like 20 or so possessions in this game. Fascinated to see if that continues or if that was just a strategy against the Suns.
-I hate everything about what this Phoenix team has done to its starting lineup. They were without Mark Williams and Oso Ighodaro tonight, so Maluach had to start. But really, the problem here is that Jalen Green and Miles Bridges are the antithesis of what made this team fun last year. They were so selfless and played for one another on defense last season. They moved the ball quicker and made better decisions. This group doesn't do that with the starters. Coming into tonight, Phoenix's starters had a negative-35.5 net rating and tonight might make that slightly better, but not much better. They got their ass kicked.
-Green's stat line looks about as good as it could. He had 20 points, four assists, four rebounds, only one turnover and shot 8 for 13 from the field. I wouldn't say that he played poorly, but I didn't love his game. I counted at least five possessions where he brought the ball up the court and shot the ball without passing, one of which was a pretty egregious one at the start of the second half where Phoenix clearly set up a Spain/stack action with Maluach and Booker, and Green just rejected the screen, drove to the rim, overpenetrated, and got stripped by McCain. Midway through the first, he had another no-pass possession where he settled for a contested midrange shot with 15 seconds left on the shot clock without trying to create anything for his teammates. When Green keeps it simple, attacking driving lanes when they come available as a slasher with his athleticism, taking open catch-and-shoot 3s, and cuts to the rim, he's an effective player. He can attack mismatches well. The problem is when he tries to isolate or play in ball-screens against high-level defenses or defenders. He also doesn't process it quickly enough and holds the ball too long upon catching it, allowing rotating defenses to catch up while he surveys. I don't think he's a fit with Devin Booker in the starting lineup.
-Bridges was even worse largely because he can't defend anyone. He gets caught in no-man's land in help way to often. He can't move his feet quickly enough on defense to deal with guards in switches. He ends up having to play too passively and is too far off of them, allowing them to get space and time to shoot. He also isn't a good enough shooter to take advantage of when he's open. He's made 33 percent from 3 over his last four years, and only has one year in his career over 35 percent despite taking six per game over the last six years. He did a nice job moving without the ball, particularly in some moments where OKC was in zone coverage. Again, he had 17 points, eight rebounds and four assists. The box score looks great. He did not play well.
-My real issue with everything Phoenix is doing here with this group is that none of it is in service of accentuating Devin Booker or the scheme Jordan Ott found success with last season. Gillespie makes life easier for Booker by spacing the court, being an aggressive point-of-attack defender, and making good decisions. Goodwin and Brooks take really tough matchups on defense and are physical. Ighodaro was out tonight, but he moves the ball quickly. But Green and Bridges just have not looked like a fit at all. Maybe it gets better as the season continues, but their careers to this point would not suggest it.
-I also haven't really loved the Khaman Maluach as a starting center experience so far. I just don't think his hands, screening or offensive processing skills are good enough yet for such a large role. Tonight he had to play 25 minutes because Ighodaro missed the game. But four turnovers in 25 minutes for such a low usage player is a killer. I also haven't loved his positioning on the glass, and even around the rim he has moments where I feel like he can get pushed around. There was a specific one at 4:14 in the third quarter where Shai just put his shoulder into his chest and drove him backwards before throwing down a dunk on him that ended up not counting because the refs called a strange foul prior. I am definitely in favor of him being a backup this year, I think he's shown enough to be useful there. But I'd probably start Ighodaro over him when he's back healthy because I think they need someone who can process the game quickly and move the ball with this starting lineup.
It was true then and even more so now with Bridges.
Book with 2 FGA’s half way through the second.
This is my biggest problem with our starting lineup. Too many guys looking to chuck it.
Doesn’t allow Book to be in his rhythm and for the Suns to play through him.
Continues to be so frustrating watching OKC games. The amount of fouls they get away with, while hitting the floor every time they’re on offense and drawing the whistle is insane.
Christopher Maddox retweeted
The Cardinals can't punch it in on seven tries from the 1-yard line.
They will lose their 10th consecutive home game, twice as long as the NFL's next-worst home losing streak. Half of those losses have been by at least 14 points.















