I'm thinking "Ok... Catch 22". IMHO, the more quickly you move, the more likely you are to make a mistake and that's not limited to what most people consider to be a "release". They forget that "patches" are really just mini-releases. They also forget that "patches" are even more tricky than a "release" because a lot of people will take short-cuts to more quickly push out a "patch" and, possibly, miss the fact that the "patch" actually broke something else. If it's an edge case (which is no less important), it may not have been tested at all.
The amount of electronics going into vehicles now just scares the hell out of me. All I really want my vehicle to do auto-magically for me is to turn the headlights on when I start it and turn them off when I turn off the engine. Of course there needs to be a manual control for if/when I want to turn the headlights off/on whether the engine is running or not. Even having computer control for spark, timing, and fuel injection is spooky to me compared to other methods. Just imagine if someone figured out the control codes to make all the vehicles in a given area go through the "slow down and die" mode that some vehicles have (like mine).
And, yeah... I love my cruise control but I could make due without it with no effort.
As a bit of a sidebar, hacking key fobs and garage door openers has been around for a very long time. It's not something new with Tesla. What is new is the ability to "patch" them remotely, which also makes them even more prone to hacking.
is pronounced "ree-bar
" and is a "Modenism
" for R
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.
"Change is inevitable... change for the better is not".
"Dear Lord... I'm a DBA so please give me patience because, if you give me strength, I'm going to need bail money too!"
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)