- cross-posted to:
- hackernews@derp.foo
- technology@lemmit.online
- cross-posted to:
- hackernews@derp.foo
- technology@lemmit.online
Our Chevy Blazer EV Has 23 Problems After Only 2 Months::undefined
Our Chevy Blazer EV Has 23 Problems After Only 2 Months::undefined
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:
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.
What do you mean? Is Wyoming big on electric cars? (No clue, not from the US)
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.
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.