The OnStar case actually makes sense since it reads and writes to various systems (when conditions that match a collision are found, it calls emergency services with your GPS location). Arguably these "features" should have been put in by the manufacturer (and currently this is happening), but as Toyota has proved, programming needs to be addressed as something more than a cost to minimized. Toyota's case was a classic example of managers having no clue what the consequences of their decisions would be. I imagine that some people got some nice bonus cash for their cost "saving" choices.
Marketing groups driving production schedules and bad project management (in my experience good project management is very nearly non-existent) are a perfect storm for this crap since we humans are terrible at writing code to begin with. On Mon, Jun 2, 2014 at 4:32 PM, Lewko, Robert <lew...@uleth.ca> wrote: > The following is an example of what you are talking about - with that auto > makers are doing their best to integrate everything from built-in game > consoles to GPS systems. > > What the f**k is a recursive algorithm doing in the ECU code for the > throttle in the Toyota's that just got recalled?!!!! Can anyone tell me > why the entertainment system and the assistance system (onstar) have to be > on the same CAN bus as the ECU and the fuel system?!!!!!! How the hell do > they expect to get these systems debugged reliably? > > Different application, but same problems have manifest themselves. I > think what is happening is that engineers who know better are not able to > reign in the marketing people. > > Corollary: bad shit happens when marketing people get too much power! > > > I couldn't agree more. In fact I find it kind of amazing that open source > > projects do as well as they do with mostly volunteer efforts. I think > > where it breaks down is when things become overly complex which is what > > the Quinn Norton article points out. Even those trying their best to > write > > good bug free software find themselves having to interface with lots of > > crap thus complicating testing. Complexity becomes a drag on the > volunteer > > effort and eventually reduces the number of eyes scrutinizing the stuff > as > > in the OpenSSL case. > > > > Welcome to the world of 0day attacks. > > > > Greg > > ----- Original Message ----- > > From: "Mel Walters" <melwalt...@telus.net> > > To: clug-talk@clug.ca > > Sent: Thursday, 29 May, 2014 11:27:47 AM > > Subject: Re: [clug-talk] Everything is broken > > > > I found Bob Beck's talk kind of encouraging. Not only because he is > > willing to admit things are wrong, BUT because Bob and people like him > > are doing something about it. > > > > Is that not what our community is supposed to be all about? Making > > things better, not just complaining? > > > > Vive le Libressl > > http://www.libressl.org/ > > > > Mel > > > > On Wed, 2014-05-28 at 13:17 -0600, Greg King wrote: > >> There was an op-ed piece in the Calgary Herald recently about how most > >> stuff on the internet is held together by gum and bailing twine. The > >> op-ed writer was basing his comments on an article by journalist/ > >> blogger Quinn Norton so I went and read the original article on a > >> website for writers called the Medium. It's an interesting rant on what > >> is going on in our connect world today. You can find it here > >> https://medium.com/@quinnnorton > >> > >> After Bob Becks talk about the issues with OpenSSL last night, this will > >> not make you feel any better about the rest of the software we use on a > >> daily basis (but most of us know some of this already). > >> > >> Enjoy (or NOT)! > >> > >> Greg > > > > > > > > > > _______________________________________________ > > clug-talk mailing list > > clug-talk@clug.ca > > http://clug.ca/mailman/listinfo/clug-talk_clug.ca > > Mailing List Guidelines (http://clug.ca/ml_guidelines.php) > > **Please remove these lines when replying > > > > _______________________________________________ > > clug-talk mailing list > > clug-talk@clug.ca > > http://clug.ca/mailman/listinfo/clug-talk_clug.ca > > Mailing List Guidelines (http://clug.ca/ml_guidelines.php) > > **Please remove these lines when replying > > > > > > _______________________________________________ > clug-talk mailing list > clug-talk@clug.ca > http://clug.ca/mailman/listinfo/clug-talk_clug.ca > Mailing List Guidelines (http://clug.ca/ml_guidelines.php) > **Please remove these lines when replying >
_______________________________________________ clug-talk mailing list clug-talk@clug.ca http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying
