We build static code analysis tools, used by companies building safety critical stuff (planes, cars,...). If you're failure mode is "there might be fatalities"

We build static code analysis tools, used by companies building safety critical stuff (planes, cars,...). If you're failure mode is "there might be fatalities" over "the app crashes", this becomes really valuable. Code quality is already quite nice, and metrics like e.g. MISRA are supported by many analyzers; but proving(!) the absence if various error classes can be handy as well. (Disclaimer: I work on the binary analyses, not on the source code analyses; so my detail knowledge on that front is not too deep). +1 for linting. If the code looks "the same" I find reviews much easier since I can focus in what it actually does (or fails to do), not on "decoding" it. Though nobody should freak out on minor variations.