4 ms·

Its hard for IT folks NOT to 'Download & Apply' the latest release to get 'that' feature. I have learned over period off time to wait for a stable release. Its

• dsr_ 14y ago
  Some obvious implementation details that spring to mind... Whoever owns the code, owns the car's liability. It is in the best interests of the manufacturer to be able to detect a vehicle not running a signed release, and require an explicit liability acceptance from the owner. Doing so whenever registration changes hands is probably a requirement, too. Or disable the ability to change the code unless you ask for an individual key that requires you to accept liability when you use it. No reason to roll out to all the 2017 Toyota AutoCorolla Xv examples at once -- after QA acceptance, do staged roll-outs to increasing group sizes. Best if the first few hundred were all Toyota employees. Roll-back to the previous version or a "known good" release, should be simple and obvious.
  • gte910h 14y ago
    "The first group that we'll roll out to is the cars that drive your children. Cheers!" Interesting, if not very threatening
• Flenser 14y ago
  The automakers could do what some web apps do, roll out new releases to a percentage of users. They could start with cars in areas where accidents are less likely to cause injuries (not densely populated, flat terrain).