alt Hacker NewsThe point is, with software you don't need tickets. Either the software is written to try to follow the law or it isn't. If it's trying, then we establish thresholds. If the company is actively trying to break the law, it should be shut down.
Tickets are a silly, roundabout way to go about it. They make sense for human drivers because they're all running different independent "brain software" and it's unrealistic for minor violations to ban someone from driving. But with shared software across a fleet, you can just require the company to fix its driving software directly when possible. Ticketing is actually counterproductive, because it allows these companies to avoid many of these fixes if the tickets are infrequent enough.
Replies
I feel like this trivializises all software development. It happens but 99% of development is done to follow the spec or law in this case. The failures or bugs are usually not intentional. You basically saying if 1 car in the fleet breaks the law shut them down? If thats a strawman im sorry but even in software algorithm have unintentional bugs and make mistakes. The same is true for human drivers but we dont revoke their licenses when they break the law we have a proportional penalty for break. If driverless cars are speeding its a slap on the wrist. If they are driving the wrong way down the freeway the penalty would be revoking licenses
> Either the software is written to try to follow the law or it isn't
Then the real world intervenes. Nobody plans to block an intersection. But a lack of planning and shits given will put one into that position even without intention.
> it allows these companies to avoid many of these fixes if the tickets are infrequent enough
Sounds fine? Like, as long as AVs and human drivers share the roads, modulating enforcement with infraction frequency seems fine.