Readit NewsChoosing to be right, is choosing to be alone.
Whatever you choose to put above trying to get along with others, limits who can be part of your group. In the extreme, you will feel absolutely justified. And yet be absolutely alone.
As an example, language communities that focus on being able to find the ideal way to program (eg Lisp) tend to splinter. The languages that achieve broad acceptance (eg Python) do things that most people recognize as bad.
This doesn't mean that we should always choose to get along, rather than being right. But failing to address emotions up front has damaged so many parts of my life, that I firmly wish that I hadn't stood for so long on how right my behavior was.
I hope that your choices are working better for you than my past choices did for me.
This should be a given for any service that others rely on, but sadly this is seldom the case.
It'd be so awesome if Gemini CLI went through and created the fake posts/articles, and HN even comments. Perhaps a bit much to ask of it?
Toyota issued multiple engine controller updates. All mfgs do, all the time.
There are no changelogs.
It would also matter what their typical car lifecycle is, it could have been just before refresh so only effected a couple years.
It could have also been bad floor mats.
We’ll never know - but the point is, that their code was so bad you COULD never know.
Are cars since then required to have formally verified codebases, or is "no one could prove [there are no bugs]" still true?
---
Trying to evaluate what happened based on observation of events alone and stats, in absence of a formal proof of issue or non-issue... the cars didn't just disappear overnight so if there was such an issue... where did it go?
This "scandal" was never about mechanical failures. It was almost certainly about driver error and mass hysteria.
As for Toyota settling, had this been Ford or Chevy, the government wouldn't have had the appetite to go after them for what was always a non-issue. It was just less expensive for Toyota to fix floor mats and pay a billion to put it all behind them.
The only thing they did in the recall was the same floor mat anchor as so many other cases.
"NASA engineers found no electronic flaws in Toyota vehicles capable of producing the large throttle openings required to create dangerous high-speed unintended acceleration incidents. The two mechanical safety defects identified by NHTSA more than a year ago – “sticking” accelerator pedals and a design flaw that enabled accelerator pedals to become trapped by floor mats – remain the only known causes for these kinds of unsafe unintended acceleration incidents. Toyota has recalled nearly 8 million vehicles in the United States for these two defects." -- transportation.gov
Cosmic rays and other wild theories over the simple theory of driver error. Even with a stuck throttle, the brakes will still stop a car (not to mention shifting into neutral still works).
I worked on a team where we had someone come in and help us improve our tests a lot.
The default LLM generated tests are bit like the ones I wrote before that experience.
I agree with this.
I've found I need a whole separate cycle of test writing to get proper (in both scope and accuracy) coverage.
It does help tremendously with all the boilerplate of tests, and it seems to be quite good at setting up numerous tests for all combinations of variables. It does have to be done explicitly, though.
And you do need to mind when a test fails whether it fixes the test or the code.