Nice cherry picking! Curious if you read the actual tweet thread, or 'collected' this knowledge via some 3rd party? Here's the context:
To be clear, I have been watching James Lock's Youtube videos since he used to post on his roadtrips w. his Model S 100DL to Yellowknife, NWT in Northern Canada. James moved to California, and became an early participant in Tesla's FSD Beta program.
Now if you've watched any of James' library of Beta test videos, he posts 1 video taken on each of 2 test loops near his home in Santa Clara. This forms a valuable resource because he has documented how FSD Beta software has evolved over the course of the test program (many thanks, and all due credit to James!).
What James does do, however, is repeatedly and continuously report the
SAME issue. I've watched him drive pass the Speed Limit sign on Plum Canyon Rd just outside his neighborhood which has
NOT been recognized for almost a year now. And James reports it repeatedly, even though the behaviour hasn't changed. Missed/late lane changes and other issues that are consistent
ARE known to the Beta team. It's just impatience.
Elon's point is simple: Tesla is running this early release Beta version v10.69 to identify any
NEW issues. There is little point in continuing to point out
KNOWN issues, as this is not the finished product. Indeed, what James would seemingly have the Tesla Autopilot team do is work on
HIS list of priorities (ie: multiple lane changes in short order after a complex mult-lane left turn). '
So DON'T work on Chuck's problem; work on MY problems.' Yeah...
Do you understand now why Elon reacted to James' tweet as an Engineering Manager, and not like some
PR poofdah? Do you think James' original tweet was appropriate, or even helpful? Will his issues still exist in 10.69.1 or 10.69.2 versions? Yes, most likely. But that's the time to advance the conversation on what to fix next, not while trying to improve and/or create a new suite of features targeting better performance in a different scenario (ie: Chuck's complex left turn).
Cheers to the FSD Beta team!