[tetha]

Good alert deduplication and dependency rules are worth so much. "Dear alerting, don't start throwing a fit about those 600 systems over there if you can't even reach the firewall all traffic to those systems goes through". Suddenly you don't get throttled by your SMS provider for the volume of alerts it tries to send, and instead just get one very spicy message.

Snark aside, this also impacts resolution time, because done well, this instantly points out the most critical problem, instead of all the consequences of one big breaking. "Dear operator, don't worry about the hundreds of apps, the database cluster is down".

[bruce343434]

This is why compilers for e.g. c++ should just halt after the first error, instead of spewing pages of template failures because of a typo elsewhere

[kyralis]

They used to, but I wouldn't want to go back to that. Believe me, compilers that continue and try their best are a massive improvement in many cases, allowing you to fix more issues between compilation attempts.

[StellarScience]

98% of the time those lengthy messages are useless, but the other 2% of the time they're critical to tracking down the problem.

A year or two ago Visual Studio added a pop-up that parses such lengthy compiler messages into a clickable tree list. I found it annoying at first, until I discovered I could dock it to the side, ignore it 98% of the time, but still go look at the details when relevant. This is an idea other compilers should copy.

Maybe ships should copy this approach too: issue fewer warnings, but provide a list of warning details for review when necessary.