Sponsored

Donald Stanfield

Well-Known Member
First Name
Donald
Joined
Jul 31, 2022
Threads
59
Messages
8,307
Reaction score
16,656
Location
USA
Vehicles
2025 R1S Tri Ascend, 2024 i4 M50
Occupation
Stuff and things
I hope a) I don't have to take it down to the SC to get this bs fixed, and b) someone is getting fired. F*cking amateur hour. I don't give props to anyone.
That's a great way to make sure you can never keep good employees. Firing someone for making an honest mistake is a great way to make sure you have no employees or worse ones than the one you got rid of. No one else is going to wind up working for you either because they will quit after getting burned out worrying constantly about being fired for the first slip up they make.

If this was willful and deliberate then yes fire that person. If the person responsible for this has a documented history of carelessness then yeah fired them. What you really should want is Wassym to figure out a policy and put a procedure in place to make sure this never happens again. Maybe separate the completed updates to a dedicated terminal and only update from there, or to develop updates on a virtual server and only move them to the real one after testing is done. Whatever, I'm not a developer so I couldn't say exactly.

What I do know is this, people make mistakes. The job of good management is to write policy and train staff on procedures so that these mistakes never happen again. That way next time the ONLY way to push a bad update would be by disregarding safeguards and that would justify insta-firing someone.
Sponsored

 

ohseedee

Well-Known Member
Joined
Mar 1, 2022
Threads
15
Messages
735
Reaction score
1,728
Location
California
Vehicles
R1T
Legacy oems: “And this is why we don’t update software on our vehicles!”

Just trying to add some humor haha… ha ha
Device updates are very very common and have been around for a very very long time. There is no real excuse for something like this this to happen ever unless your process is broken. I cant think of any other time I had an OTA take a device down. Hell my 7 year old microwave gets regular OTAs and I’ve never not been able to warm up my lean cuisines.
 

SSteveEV

Well-Known Member
First Name
Spencer
Joined
Nov 3, 2022
Threads
7
Messages
1,319
Reaction score
1,795
Location
Michigan
Vehicles
R1T, etc
Clubs
 
Just curious, we’re you fired every time you made a mistake? ??
were*

"You're FIRED!"

Sorry couldn't resist; I agree with your above point that mistakes happen and are teaching moments. I'm just going to assume you have an android because mine has been autocorrecting that incorrectly for me constantly lately and it drives me nuts.
 

ohseedee

Well-Known Member
Joined
Mar 1, 2022
Threads
15
Messages
735
Reaction score
1,728
Location
California
Vehicles
R1T
That's a great way to make sure you can never keep good employees. Firing someone for making an honest mistake is a great way to make sure you have no employees or worse ones than the one you got rid of. No one else is going to wind up working for you either because they will quit after getting burned out worrying constantly about being fired for the first slip up they make.

If this was willful and deliberate then yes fire that person. If the person responsible for this has a documented history of carelessness then yeah fired them. What you really should want is Wassym to figure out a policy and put a procedure in place to make sure this never happens again. Maybe separate the completed updates to a dedicated terminal and only update from there, or to develop updates on a virtual server and only move them to the real one after testing is done. Whatever, I'm not a developer so I couldn't say exactly.

What I do know is this, people make mistakes. The job of good management is to write policy and train staff on procedures so that these mistakes never happen again. That way next time the ONLY way to push a bad update would be by disregarding safeguards and that would justify insta-firing someone.
Agree with what you said in general, but what about those that defined and oversee the OTA process? If some low level employee clicked X instead of Y, I agree. Shit happens. But who was the person or persons that designed that X and Y button next to each other without a 2nd pair of eyes in the process, etc.?

Unless it was negligence, I’d give the fat finger a pass. But if this was a process failure I might ask for a resignation at the top...
 

Sponsored

SANZC02

Well-Known Member
First Name
Bob
Joined
Feb 11, 2021
Threads
50
Messages
7,409
Reaction score
12,702
Location
California
Vehicles
Tesla Model S, LE - R1S
Occupation
Retired
But did any of his mistakes result in 100s of millions of dollars worth of automobiles not working?

Very much depends on the circumstances, but I could see one or more jobs being lost as a resonable outcome here.
It is a very visible error for sure, people will be called to the carpet on this. If they were not following the existing release procedure it will be one thing. Once they finish the RCA for this they will be adding additional checking into the procedure.

One thing I’m sure we will see come from this is the first couple of days they will roll out way fewer packages. We probably will not see 1000s go out the first couple of days like we have seen before. There will be a lot more “still waiting” posts in these threads.
 

DuoRivians

Well-Known Member
Joined
Dec 30, 2022
Threads
257
Messages
3,809
Reaction score
9,076
Location
California
Vehicles
R1T, R1S
Device updates are very very common and have been around for a very very long time. There is no real excuse for something like this this to happen ever unless your process is broken. I cant think of any other time I had an OTA take a device down. Hell my 7 year old microwave gets regular OTAs and I’ve never not been able to warm up my lean cuisines.
Yes, Rivian admits they made a bad error and aren’t making up excuses for it
 

Mark_AZR1T

Well-Known Member
Site Sponsor
First Name
Mark
Joined
May 28, 2021
Threads
42
Messages
2,220
Reaction score
3,866
Location
Gilbert, AZ
Website
jackpucks.com
Vehicles
R1T Launch, R1S Canyon Red
Clubs
 
I'm in Mexico, feeling fortunate that I did not try to update the truck. I wonder what Rivian would have done for me if they had bricked my truck way down here...
Bryce Menzies has an extra spot on his trailer.....
 

Nikhiluor

Well-Known Member
First Name
Nikhil
Joined
Sep 16, 2023
Threads
14
Messages
81
Reaction score
71
Location
Cupertino
Vehicles
R1S
This will hurt Rivian …I am glad, I had decided to wait for update this time but got a different issue right exact time …”Airbags need service “…
 

SANZC02

Well-Known Member
First Name
Bob
Joined
Feb 11, 2021
Threads
50
Messages
7,409
Reaction score
12,702
Location
California
Vehicles
Tesla Model S, LE - R1S
Occupation
Retired
were*

"You're FIRED!"

Sorry couldn't resist; I agree with your above point that mistakes happen and are teaching moments. I'm just going to assume you have an android because mine has been autocorrecting that incorrectly for me constantly lately and it drives me nuts.
Can I be fired from retirement…?
 

Sponsored

Jdrexler

Member
First Name
John
Joined
Mar 17, 2023
Threads
1
Messages
11
Reaction score
17
Location
Reno, NV
Vehicles
Rivian R1T Quad/Large. 2009 Toyota Tundra.
Occupation
Healthcare
I had the OTA fail at 90% as well, like many others here. I just ended a chat with Rivian, and he instructed me to put the vehicle into a deep sleep mode so it will be ready to receive the OTA fix once it's ready. The plan at this point is to automatically push the OTA fix to affected VINs without any required action on the part of the owner, if I understood that correctly.
 

JamboF4

Well-Known Member
First Name
Jim
Joined
Oct 8, 2021
Threads
18
Messages
543
Reaction score
404
Location
Ponte Vedra Beach, FL
Vehicles
R1T, C8 ZO6, Tacoma, Arcimoto
Occupation
Retired airline Captain
Update failed to install, after reaching 90%. I’m on chat
Center display is blank, but periodically shows the large Rivian logo like the software is starting up. The Driver display shows Ready and gear selector, range remaining.
Do not bother to call Reggie, Rickie, Ronnie or Robbie on the Service chat. Useless. Uber credits were all he could suggest.
 

s00n

Well-Known Member
Joined
Sep 28, 2022
Threads
12
Messages
196
Reaction score
314
Location
CO
Vehicles
R1S - Cayenne S - Jeep LJ Rubicon Turbo
That's a great way to make sure you can never keep good employees. Firing someone for making an honest mistake is a great way to make sure you have no employees or worse ones than the one you got rid of. No one else is going to wind up working for you either because they will quit after getting burned out worrying constantly about being fired for the first slip up they make.

If this was willful and deliberate then yes fire that person. If the person responsible for this has a documented history of carelessness then yeah fired them. What you really should want is Wassym to figure out a policy and put a procedure in place to make sure this never happens again. Maybe separate the completed updates to a dedicated terminal and only update from there, or to develop updates on a virtual server and only move them to the real one after testing is done. Whatever, I'm not a developer so I couldn't say exactly.

What I do know is this, people make mistakes. The job of good management is to write policy and train staff on procedures so that these mistakes never happen again. That way next time the ONLY way to push a bad update would be by disregarding safeguards and that would justify insta-firing someone.
Agree with all your points.

However is firing someone who makes an honest mistake that gets people killed acceptable? I'd say that's a bit dramatic, but having people drive around with no speedo probably isn't the best idea either.

I guess we'll just let them say "oops, my bad" and move on. At least they're owning it.
Sponsored

 
 








Top