this post was submitted on 21 Dec 2023
35 points (80.7% liked)

Technology

59598 readers
3536 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 content.
  3. Be excellent to each another!
  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, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago
MODERATORS
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
35
Our Chevy Blazer EV Has 23 Problems After Only 2 Months (www.edmunds.com)
submitted 11 months ago by [email protected] to c/[email protected]
27 comments fedilink hide all child comments
 

Our Chevy Blazer EV Has 23 Problems After Only 2 Months::undefined

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 13 points 11 months ago (1 children)

I'll be honest, this is less than 20 minutes of just ERROR log lines (nevermind warnings) in the application I'm working on.

Is that bad? Sure. But a large portion is also because it's over a hundred individual software components and logging has been implemented badly with software that grew over time. Just saying that there's a log message means ~nothing.

In fact I would argue that if done well, this is the way it should work:

  • Display to the user if there's an immediate problem. Something needs fixing or urgent investigation.
  • Persist it to a warning-log if it's something that's not bad, stuff all works or redundancy is still holding easily (meaning it's still redundant, say 1 out of 4 redundant units failed or a component stopped sending diagnostics but is still working), and the next time it's in for something else, a mechanic/technician can also quickly check whether there's a real problem.
[–] [email protected] 2 points 11 months ago (1 children)

Here's to betting you wouldn't hold this opinion stuck on the side of the highway in the middle of Wyoming or something similar.

[–] [email protected] 1 points 11 months ago (1 children)

What do you mean? Is Wyoming big on electric cars? (No clue, not from the US)

[–] [email protected] 1 points 11 months ago (1 children)

Wyoming contains some of the longest stretches of US road without available services. IE: If you get stuck because your car broke down, you’re gonna have a bad time.

[–] [email protected] 3 points 11 months ago

Oh, in that case I might have worded my post badly. I explicitly meant non-critical stuff would make sense to not openly show. There's so much that can go beepy beep on moder wheeled computers that showing it all to the user would result in needing 10x the telephone support staff.

And there's a lot that's perfectly fine to leave as it is, and just have someone look at it the next time it's in for a check-up anyways.

For stuff where the car can break down, yeah fuck no, don't hide that. I was mostly musing how to do a shown/hide split in a sensible manner.