Skip to content
HomeVideosBooksBlogs
AllTop postsTopics
Podcasts
HistoryListsWatch laterLiked videosFollowing

The videos, books, blogs and podcasts Hacker News keeps recommending, all in one place.

VideosBooksBlogsPodcastsAboutPrivacySettings

Data from Hacker News, HackerTube, HackerBooks, HackerBlogs and Open Library. Credits · Not affiliated with Y Combinator.

HomeVideosBooksBlogsPodcasts
Ctrl K

    Safety Research & Strategies

    safetyresearch.net · Company blog · on HN since 2014

    Safety Research & Strategies is a safety consultancy that publishes analyses of auto defects, including Toyota's firmware and Tesla's Autosteer.

    Visit blogHN submissions
    ProgrammingScienceCulture & Society
    What HN says

    HN commenters cite it for the Toyota unintended acceleration code review by Michael Barr and for its critique of NHTSA's Autosteer safety claim.

    Stats for nerds
    72HN people shared it
    13linked in comments
    428story points
    Apr 2026last shared
    2015people per year2026

    Top posts on HN

    1. 1
      Toyotas Unintended Acceleration and the Big Bowl of “Spaghetti” Code (2013)
      30 people · 199 points · first shared 2015 · 145 comments on HN
    2. 2
      Toyota Unintended Acceleration and the Big Bowl of “Spaghetti” Code (2013)
      4 people · 96 points · first shared 2015 · 106 comments on HN
    3. 3
      NHTSA’s Implausible Safety Claim for Tesla’s Autosteer Driver Assistance System [pdf]
      2 people · 81 points · first shared 2019 · 39 comments on HN
    4. 4
      Toyota unintended acceleration and the big bowl of "spaghetti" code (2013)
      4 people · 35 points · first shared 2021 · 54 comments on HN
    5. 5
      Toyota Unintended Acceleration and the Big Bowl of “Spaghetti” Code
      1 person · 10 points · first shared 2014 · 2 comments on HN
    6. 6
      2005 Camry L4 Software Analysis (2011) [pdf]
      18 people · 4 points · first shared 2015 · Discussion on HN
    7. 7
      Testimony regarding review of Toyota code in infamous “stuck” accel case [pdf]
      2 people · 2 points · first shared 2015 · 2 comments on HN
    8. 8
      The Dark Side of Lighters (2011)
      1 person · 1 points · first shared 2018 · Discussion on HN
    9. 9
      Quality control systems corp sues dot tesla data
      3 people · first shared 2018
    10. 10
      Tipping point
      2 people · first shared 2018

    What HN people wrote when they linked it

    • rl3Jan 2020

      That's a good question.

      The first thing that came to mind for me was the bad, namely Toyota's unintended acceleration debacle some years back.[0] If anything this illustrated (at the time) a woeful lack of any proper software engineering practices at Toyota that was to some degree indicative of a larger problem across their entire industry. No doubt this was due in large part to Japan's corporate culture and their admirable-yet-deleterious work ethic.

      As far as the good, the first place I thought to look was Hideo Kojima's games, namely their engine technology. The history of the Fox Engine[1] and in particular the Decima[2] engine appears very interesting. Kojima games are almost always bleeding-edge with respect to rendering technology.

      There's of course Nintendo. I had a friend who worked in software QA there, and there wasn't much good to say about it. That said, it was some years ago and one person's experience in one location.

      Japan used to be a leader in robotics, though I'm not sure how true that is anymore what with Boston Dynamics in the spotlight in recent years.

      To answer your question however, my guess would be no, probably not—Japan is likely playing catch up right now in terms of software practices. The Japanese development teams and researchers that do output quality, I'd imagine they just use common sense good practices recognized internationally. Namely: hire high-caliber talent, pay them well and don't overwork them. Quality usually follows regardless…

    • sedachvNov 2016

      > It's not just money. It's paperwork, bureaucracy, and ultimately not effective. Practically, the only way to ensure safety is to take down the internet.

      https://logfall.wordpress.com/all-or-nothing-fallacy/

      We can and should be making incremental improvements to technology. Continuing to use methods that are known to be faulty is gross negligence in the legal sense: https://en.wikipedia.org/wiki/Gross_negligence

      We do not see enough lawsuits around software negligence today because companies are under no obligation to release source code - there is no way to tell how or why or even whether software is defective. This was a major issue in the investigation of the Toyota unintended acceleration scandal. The investigation uncovered major, obvious code quality problems, ultimately concluded the fault was caused by software (something Toyota denied, and without the investigation, consumers never would have learned), and I hope becomes a precedent: http://www.safetyresearch.net/blog/articles/toyota-unintended-acceleration-and-big-bowl-%E2%80%9Cspaghetti%E2%80%9D-code

      IMO if poor coding practice is gross negligence, it follows that failing to reveal the source code constitutes intent: poorly developed closed-source software is criminal negligence.

    • MereInterestFeb 2020

      Reading through the crash test procedure, it is astounding how little attention is paid to pedestrians.

      1. Front crash test. Procedure: Crash car into stationary barrier at 35 mph. Is also applicable to face-to-face crash with car of same size, going at same speed.

      2. Side crash test. Procedure: Slam concrete block into side of stationary car at 38.5 mph.

      3. Side pole test. Procedure: Drag car sideways towards a pole.

      4. Rollover resistance. Procedure: Compare the cars footprint to the height of the center of gravity.

      The biggest thing to notice is that not one of these metrics involves pedestrians. Metrics 1-3 can be easily improved by making a bigger car, elevating the passengers and providing more crumple room. Metric 4 is unaffected, as the track width is increased to compensate.

      If a low sedan hits a pedestrian, the pedestrian rolls over the car, having a lower impulse given over a longer period of time. If a high SUV hits a pedestrian, the pedestrian is knocked back, having a higher impulse given over a shorter period of time. Safety ratings need to account for the danger cars pose to others.

      Source: https://www.nhtsa.gov/ratings

      Source (SSF): https://www.safetyresearch.net/rollover-stability

    • novaleafJun 2019

      Whenever I see articles like this, I like to remind people that a great production system doesn't make a company more honest or accountable.

      Unintended acceleration flaw in Toyota models around 2005 to 2011, due to firmware bugs: http://www.safetyresearch.net/blog/articles/toyota-unintended-acceleration-and-big-bowl-%E2%80%9Cspaghetti%E2%80%9D-code

      Great for USA customers. They were made whole.

      I personally was driving a 2011 Toyota minivan in Thailand in 2013 when I suffered this firmware bug. Toyota refused to consider it was anything other than driver fault. I was only going 5kph when it happened so no damage, but damn scary as hell. No recall in that country, and unless dealers did a covert firmware upgrade during maintenance, the flaw still exists in similar model years.

    • JackMcMackMar 2022

      Have you seen the report on the Toyota source code?

      http://www.safetyresearch.net/Library/BarrSlides_FINAL_SCRUBBED.pdf

      https://news.ycombinator.com/item?id=9449559

      "In a nutshell, the team led by Barr Group found: “a systematic software malfunction in the Main CPU that opens the throttle without operator action and continues to properly control fuel injection and ignition” that is not reliably detected by any fail-safe."

      And the black box could fail to record any braking input in such cases.

      That's not good! People died! And you would have a hard time convincing a jury that the driver was not at fault, if not for the thorough independent code review.

      And that's the safety critical stuff, now imagine all the code for the infotainment systems.

    • seanp2k2Dec 2021

      I agree; it's like all the rollaway accidents that happen now because of electronic shifters: https://www.safetyresearch.net/the-persistence-of-rollaway/

      Design matters, and bad designs can literally be deadly. Why auto mfgs feel the need to "innovate" with shifter designs is beyond me. The worst part is how every mfg seems to be implementing a different design of bad electronic shifters, from wheels and touchscreens to one-click-at-a-time joysticks to single-function pushbuttons for some gears with others on a scroll wheel. They've taken something and made it worse with no benefit to the user. At least with those auto-flushing toilets, the intention was good, even if the implementation is still somehow so awful decades later.

    Related

    Better Embedded Softwarebetterembsw.blogspot.com20 people

    A Case Study of Toyota Unintended Acceleration and Software Safety

    Better Embedded Software
    Personal · last shared 2025
    KeenLab Blogkeenlab.tencent.com22 people

    Exploiting Wi-Fi Stack on Tesla Model S

    KeenLab Blog
    Company · last shared 2024
    beza1e1beza1e1.tuxen.de120 people

    A collection of things that are Turing-complete by accident (2013)

    beza1e1
    Personal · last shared 2026
    MSRC Blogmsrc.microsoft.com240 people

    SolarWinds hackers were able to access Microsoft source code

    MSRC Blog
    Company · last shared 2026
    FireEye Blogfireeye.com158 people

    Highly Evasive Attacker Leverages SolarWinds Supply Chain

    FireEye Blog
    Company · last shared 2023
    Car and Driver Blogblog.caranddriver.com65 people

    New Jersey legalizes direct Tesla sales

    Car and Driver Blog
    Company · last shared 2018
    Trend Micro Blogblog.trendmicro.com112 people

    First Java Zero-Day Attack in Two Years Targets NATO and US Defense Organizations

    Trend Micro Blog
    Company · last shared 2020
    Positive Technologies Blogblog.ptsecurity.com43 people

    Disabling Intel ME 11 via undocumented mode

    Positive Technologies Blog
    Company · last shared 2021