this post was submitted on 15 Nov 2023
226 points (98.3% liked)

Technology

73939 readers
4971 users here now

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

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots

founded 2 years ago
MODERATORS
L3s@lemmy.world
enu@lemmy.world
technopagan@lemmy.world
L4s@lemmy.world
L3s@hackingne.ws
L4s@hackingne.ws
226
Rivian says "fat finger" caused software update to brick infotainment systems, physical servicing may be required (driveteslacanada.ca)
submitted 2 years ago by L4s@lemmy.world to c/technology@lemmy.world
43 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
[–] floofloof@lemmy.ca 11 points 2 years ago* (last edited 2 years 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.

[–] Wahots@pawb.social 4 points 2 years 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.