and how not do do it. Interesting read. Frightening too. Excerpt:
http://www.safetyresearch.net/blog/articles/toyota-unintended-acceleration-and-big-bowl-spaghetti-code
and how not do do it. Interesting read. Frightening too. Excerpt:
http://www.safetyresearch.net/blog/articles/toyota-unintended-acceleration-and-big-bowl-spaghetti-code
The less I know about car software the better. German c’t magazine had a fascinating article about the Jeep hack. I doubt that any other car maker is better. They seem to have to learn all the things again that the software industry has learned in the last 20 years.
Heck. Difficult to go from mechanical parts to software.
Maybe if they start by hiring good with normal monthly pay ($) insted of converting someone and paying it the lowest possible
Also, not developing in a hurry can help (for some, others that love been in that state ).
Very interesting read. The management obviously had no clue whatever with software development. I heard that modern cars have more than 100.000.000 code lines (yes, one hundred million). I work as enterprise architect in a very modern software factory for the financial world. Our flagship has about 1.000.000 code lines and it takes an army of test engineers and tons of automated test tools to deliver stable and predictable releases. I wonder how one tests one hundred million code lines?
That’s incredibly enlightening. Thanks Ulrich!
A modern automobile has not one but several computers. I guess the figure of 100,000,000 is the total. Yet, it is pretty frightening.
I couldn’t believe it but it’s true. Ofcourse it’s the total of several more or less indepentent computing components. The implementation of automated driving will add a few lines I’m sure.
This is a major problem in the industry, especially where IT is part of a larger product. A software company might have coders all the way up to the CEO. But in many companies code is Egyptian hieroglyphics to middle management and above.
Another major problem. I’ve witnessed one too many engineering teams disbanded, and their creations nose dive, because management honestly believed that offshore team could do equal work for less then local minimum wage.
[quote=233013:@Daniel Taylor]This is a major problem in the industry, especially where IT is part of a larger product. A software company might have coders all the way up to the CEO. But in many companies code is Egyptian hieroglyphics to middle management and above.
Another major problem. I’ve witnessed one too many engineering teams disbanded, and their creations nose dive, because management honestly believed that offshore team could do equal work for less then local minimum wage.[/quote]
Yes, but the developers themselves are often not the most communicative types So the interaction between these two levels are rudimentary at best. Managers are challenged on two things only: time and money. In their world view is no room for complexity.
A bit late in this thread but take a look in this graph; it compares lines-of-code - stunning.
How are they counting lines of code, when they can’t see the source code? Or are they counting machine code instructions?!?