Ok, a few comments.
First, there really is no reason for blasting the stereo or driving over 80- so I don't see an issue with that. On that same note, I see this as more of a "marketing" gimmic than anything else; to make parents feel better for their lack of time spent teaching their kid how to drive.
What I do have a problem with is the innability to disable traction control (at least within certain limits). I grew up in areas where we got a lot of snow and traction control is AWFUL if you are trying to get your car unstuck. I completely understand the need for traction control over 15mph because it DOES help you maintain control (my Saabs ESC is awesome at speed); but for that initial "getting the car moving" it can be nothing but an unpredictable hindrance...just when you go to rock the car- the power cuts out...awful, or sometimes it doens't cut and the car moves more than expected...not fun. Now some might say "well they shouldn't drive when its snowing". What I am talking about is getting out of that "leftover from the plow around your parking spot" snow...you don't always have a shovel handy and there is definately a real chance of getting stuck somewhere if you can't rock the car effectively in some of our snowier climates.
In my opinion the BEST safety equipment is driver training. I cannot say enough for real behind-the-wheel defensive driver training. Not the "driving school" you take to get your permit (in NJ anyway); but where they simulate "bad" conditions and teach you how to drive safely through them.
To those of us familiar with software we look at software quality a critical issue. To those of us who are not familiar all we care about is "does it work". It sounds like to date much of your ad-hoc developement has "just worked". What you need to do to convince those in your management of the importance of software quality is to show them how it will benefit the company's bottom line. I would suggest looking up different software quality processes/management systems and then putting together a sound (not exaggerated) business case that will show your management how software quality processes/management will benefit shareholders. This is not an easy thing to do as most engineers see the "obvious" benefits; but remember- these are not engineers you are working with and you need to show why a certain quality assurance process turns into $$$ at the end. It is hard work but if you can tie sound engineering principles to business benefits...you will probably end up getting a promotion ontop of just the quality control system you want. Sorry for any grammatic errors here- not enough time to proofread.
Slashdot Mirror
Ok, a few comments. First, there really is no reason for blasting the stereo or driving over 80- so I don't see an issue with that. On that same note, I see this as more of a "marketing" gimmic than anything else; to make parents feel better for their lack of time spent teaching their kid how to drive. What I do have a problem with is the innability to disable traction control (at least within certain limits). I grew up in areas where we got a lot of snow and traction control is AWFUL if you are trying to get your car unstuck. I completely understand the need for traction control over 15mph because it DOES help you maintain control (my Saabs ESC is awesome at speed); but for that initial "getting the car moving" it can be nothing but an unpredictable hindrance...just when you go to rock the car- the power cuts out...awful, or sometimes it doens't cut and the car moves more than expected...not fun. Now some might say "well they shouldn't drive when its snowing". What I am talking about is getting out of that "leftover from the plow around your parking spot" snow...you don't always have a shovel handy and there is definately a real chance of getting stuck somewhere if you can't rock the car effectively in some of our snowier climates. In my opinion the BEST safety equipment is driver training. I cannot say enough for real behind-the-wheel defensive driver training. Not the "driving school" you take to get your permit (in NJ anyway); but where they simulate "bad" conditions and teach you how to drive safely through them.
To those of us familiar with software we look at software quality a critical issue. To those of us who are not familiar all we care about is "does it work". It sounds like to date much of your ad-hoc developement has "just worked". What you need to do to convince those in your management of the importance of software quality is to show them how it will benefit the company's bottom line. I would suggest looking up different software quality processes/management systems and then putting together a sound (not exaggerated) business case that will show your management how software quality processes/management will benefit shareholders. This is not an easy thing to do as most engineers see the "obvious" benefits; but remember- these are not engineers you are working with and you need to show why a certain quality assurance process turns into $$$ at the end. It is hard work but if you can tie sound engineering principles to business benefits...you will probably end up getting a promotion ontop of just the quality control system you want. Sorry for any grammatic errors here- not enough time to proofread.