a lot of things about this car are getting the best of me. I need to pull back some and become less invested. it's either a love/hate or hate/love thing.
That's the difference between FB and social media (for bloggers and budding influencers) vs a forum.
I think you need to stop pulling, regardless of what direction it is.
I'm not competent to judge about their implementation.
Will they eliminate the problem or just the message?
A common software statement: works as designed.I'm not competent to judge about their implementation.
But I think it would be "possible", although I don't think this is a realistic scenario. They will most likely be satisfied if it "works" at all and meets all legal requirements and all country specifics for each individual country and all specifics for each specific vehicle configuration. That's a lot of variations, and you certainly won't voluntarily add any more.
I've seen so much junk software in my life that I've long since stopped wondering about software-destroyed equipment, missile crashes, and accidental bombings of friendly troops.
Many years ago (at least three decades) I had to track down a bug in a commercial software. This error had plagued the company (a bank ...) for a long time and simply could not be found. The module in question was a source code with about 8000 lines of code, and it took me a very long time to get to the bottom of it.
I went through the software step by step with the debugger and on the third day finally found the routine where the problem was triggered.
In it I found the comment of one of the developers involved. It read
"If you come here, it's all too late".
This developer had detected that the underlying concept was simply wrong - but had no chance to do something against it. It is like building a house ground up and start with the roof: You can't put anything useful on it. Hence the comment. In the code an uncontrolled "longjump" followed which discarded the current transaction and did not process it further. A real "Martin Baker": pull the trigger and get out of here.
Catastrophic.
The hammer was what happened when I documented the facts and meticulously explained them one floor up: they marked the error as tolerable and thanked me.
Everything remained as it was.
That was the day I realized what software actually is: It is the incarnation of a collection of wrong concepts from people who didn't understand the problem coupled with the inability to recognize such concepts as wrong and to stand up as a developer against those who are responsible for it.
And in today's projects, there are no longer five or ten people involved in the development, but hundreds, from the legislator to the architect to the developer.
And somewhere in that long chain, someone didn't understand what it was all about, or put their personal piss mark, or simply had been pissed off with everything.
Of course there is the famous QC. But they also have a problem: It must be ready tomorrow.
I did and still do experience the very same in different flavors of issues. My spouse is in the very same business and agrees in whole. there is one thing that comes in regulated business on top, not just QC but compliance to certain regulations. In banking a bit more in automotive industry not yet that strict but as we know since diesel gate.. authorities look quite close on vehicles now. So one more the (compliance guys ) in the food chain who has no clue. Regulation beyond reality. Everything else @emax put down here is sooo true.I'm not competent to judge about their implementation.
But I think it would be "possible", although I don't think this is a realistic scenario. They will most likely be satisfied if it "works" at all and meets all legal requirements and all country specifics for each individual country and all specifics for each specific vehicle configuration. That's a lot of variations, and you certainly won't voluntarily add any more.
I've seen so much junk software in my life that I've long since stopped wondering about software-destroyed equipment, missile crashes, and accidental bombings of friendly troops.
Many years ago (at least three decades) I had to track down a bug in a commercial software. This error had plagued the company (a bank ...) for a long time and simply could not be found. The module in question was a source code with about 8000 lines of code, and it took me a very long time to get to the bottom of it.
I went through the software step by step with the debugger and on the third day finally found the routine where the problem was triggered.
In it I found the comment of one of the developers involved. It read
"If you come here, it's all too late".
This developer had detected that the underlying concept was simply wrong - but had no chance to do something against it. It is like building a house ground up and start with the roof: You can't put anything useful on it. Hence the comment. In the code an uncontrolled "longjump" followed which discarded the current transaction and did not process it further. A real "Martin Baker": pull the trigger and get out of here.
Catastrophic.
The hammer was what happened when I documented the facts and meticulously explained them one floor up: they marked the error as tolerable and thanked me.
Everything remained as it was.
That was the day I realized what software actually is: It is the incarnation of a collection of wrong concepts from people who didn't understand the problem coupled with the inability to recognize such concepts as wrong and to stand up as a developer against those who are responsible for it.
And in today's projects, there are no longer five or ten people involved in the development, but hundreds, from the legislator to the architect to the developer.
And somewhere in that long chain, someone didn't understand what it was all about, or put their personal piss mark, or simply had been pissed off with everything.
Of course there is the famous QC. But they also have a problem: It must be ready tomorrow.
how???
I have practised it several times now. If you have a seat belt on, you can open the driver's door while driving. I have only tried it in first gear for manoeuvring.
I don't like it. No good on the private property farm if you need to move gate to gate... I'll have to adjust 20 Plus years of bad habit!
The puddle light on the passenger side of my car does not work (the driver’s side seems fine)Noticed last night that my puddle lamps weren’t working. Lucky it wasn’t raining.
As I get over the euphoria of having my vehicle at home, time I started to list any defects for the dealer to address when updating software.
From the Ineos Manual page 44 on seat belts:-
Nice photo. I also see it states nose down rather than nose up in the display?
