Technology

59298 readers

4979 users here now

This is a most excellent place for technology news and articles.

Our Rules

Follow the lemmy.world rules.
Only tech related content.
Be excellent to each another!
Mod approved content bots can post up to 10 articles per day.
Threads asking for personal tech support may be deleted.
Politics threads may be removed.
No memes allowed as posts, OK to post as comments.
Only approved bots from the list below, to ask if your bot can be added please contact us.
Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago

MODERATORS

[email protected]

247

Rivian says "fat finger" caused software update to brick infotainment systems, physical servicing may be required (driveteslacanada.ca)

submitted 1 year ago by [email protected] to c/[email protected]

46 comments fedilink hide all child comments

Rivian says "fat finger" caused software update to brick infotainment systems, physical servicing may be required::Today’s cars are more like computers on wheels, and even a seemingly routine software update can lead to unexpected consequences. Rivian unfortunately experienced a “fat finger” mishap with their latest software update, bricking infotainment systems [...]

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 12 points 1 year ago* (last edited 1 year ago) (1 children)

in the longer run.

I have yet to work for a company where management cares about this. It's always about what can be sold next week if we rush it enough. Or, more commonly, what was sold weeks ago without any consultation with the technical team.

[–] [email protected] 4 points 1 year ago

It's a problem everywhere. Rush to build something, then don't actually finish it, or iron out the bugs before moving on to the next sexy thing. Management wonders why everyone is on the super ancient, rocksolid platform and hasn't really taken the bait on the series of products that have an "agile" development cycle and were dropped after about 5 years.

Guys....my entire team knows the issue. Support your damn products for years. Commit to improvements for a decade, and help people transition to a new product when the old one has to be sunsetted for technological or knowledge worker retirement reasons.