+1. Their software is behind machinery that is directly responsible for the safety of people. I once contracted for a company that developed software for the military. I'm not going to say exactly what I worked on but if there were bugs, people may be seriously injured. It had the most stringent change control process I've ever experienced. Developers did not have direct access to the software repository. Before we were even allowed to change one line of code, we had to attend change control meetings to justify what files we needed to modify, why we needed to change it and provide stacks of documentation for support. Only after it was approved were we allowed access to files. Before code commits were done, we had attend another change control/code review meeting with a team of guys with decades of software development experience. Code was scrutinized line by line, tons of questions from the team and another stack of paper documenting and supporting every change with proof of dev testing every change. The rejection rate was high and if one single person was uncomfortably with the code or if you were unable to answer one question, you changes were not going in. That was the only place I worked at where there were no bugs released in production, ever. Tesla releasing something with a bug that didn't exist before shows me their software development and software release control is broken. People's lives are on the line. While there's probably no need for Tesla to follow the stringent process with my prior employment, they should not be releasing their software like its a website or system where the worst consequence is losing revenue.