Actually, I was *just* thinking that if I were in charge of Tesla development, I would put together a program where programmers could offer to fix various bugs that were bugging them for free. I would bet Tesla would get loads of offers for free development work.
Just to take a minor example, some of the problems with FSD is caused by bad map data. I drive on a local rural road that has posted 25 mph speed limits, but for some reason, the car thinks a 1/8 mile stretch in the middle of it has a 45 mph speed limit, so it speeds up and then slows down when doing FSD. The reverse also happens to other people, which is more aggravating. Anyways, you can conceive of a whole bunch of algorithms to find and clean up bad data like this which would make FSD that much better.
Since I'm a retired programmer, I would love to work on this particular problem, which would a nice easy bit of work, no stress, and would help everyone.
I have those exact problems near my home and on my commute.
35mph road with houses on both sides...FSD jumps to a 55mph speed limit for a short section, until it sees the next 35mph sign. It used to accelerate much harder for the "fast" section, and I think that has at least tamed a little lately, but it still aims to go much faster than it should so I need to be ready to scroll-down the speed.
Some time ago, another nearby area had a 25mph speed limit sign that the car would literally display on-screen, but ignore and target its own 55mph speed limit. That one got fixed, so FSD follows the correct 25mph limit now.
And for FSD trying to go too slow: much of my commute is through somewhat remote desert areas, on 1-lane-each-way roads with an assumed 55 mph speed limit. There are sections where FSD assumes a 25mph speed limit, so I need to correct that upward. In one particularly annoying spot, it assumes a 25mph speed limit for a short section -- I get that corrected with the scroll wheel -- then the map data jumps very briefly to the correct 55, and then drops back down to 25mph again, demanding another manual correction.
Also a couple sections with oddly placed speed limit signs (one sign is far across a dirt shoulder from the road, and another sign is mounted low on the pole, beneath another road sign) that FSD doesn't acknowledge...so I'm accustomed to manually adjust for those too.
A couple years ago, Elon's line about FSD (and really all the automated features in the cars) was that "any [user] input is error [on the car's part]." So, on some level, I tell myself that as I make inputs to correct FSD's errors, that might be getting logged somewhere, and Tesla's engineers are just working their way down the list of priorities to correct the errors over time.
Related thought: Does anybody else feel like FSD puts them in an odd/unique state of mind? For me, it's like a combination of opposites -- it really is a more relaxing drive, but at the same time I feel more focused and vigilant as I watch for any need for my input/correction.
Or similarly:
