2026-08-05 18:44 UTC
@pac85@social.treehouse.systems really insightful posts, thanks for taking the time to write it up in so much detail.
Back in the day when I worked on static analysis tools, which had a fair number of false positives, everybody’s first reaction was to put them into the build process and crank the warnings up to the highest level … which had the same kind of counterproductive effects you’re describing here. The more successful deployments made it easy for devs to run the tools on their own before checking in (if they wanted to) and focused the build checking on high-accuracy messages and high-severity bugs where it was okay to wade through some false positives because the real ones were so consequential. Sometimes less really is more!
Replies (1)
-
@abartlet@mastodon.nzoss.nz 2026-08-08 20:57
@jdp23@neuromatch.social @pac85@social.treehouse.systems Even more problematically, incorrect warnings often lead to real bugs as the (lack of) warning is considered the only arbitrator of correctness, not the actual function of the program. The Debian weak keys issue came from a "shut up the checker" fix without deep thought as to what was being done and why. At other times it just creates even more complex code to attempt to go beyond what the checker can understand.