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

  • Carighan Maconar@lemmy.world
    link
    fedilink
    English
    arrow-up
    6
    ·
    11 months ago

    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.