* better product quality
Static analysis tools detect 'technical debt', 'smelly code' and 'bad practices'. These might be OK in the short-term, but over time will slow down your development cycle and wreck your product<ref>or worse: Software errors have famously caused rockets to miss targets; cars to kill people, trains to crash</ref>.
Some people don't like static analysis. Frankly, that might just be because you're OK producing software that has bugs. Or else I think it's either because those people are short-sighted in ways that extra process means "slow delivery" for them. Or, they don't know computer <nowiki>'''</nowiki>science<nowiki>'''</nowiki> and so if you mention topics like [[wp:Reification (computer science)]], they get uncomfortable and defensive. No matter the real reason, I don't believe you can be a professional software developer and disclaim the benefits and utility of static analysis tools in producing better quality software with less time and effort.
===Psalm===
https://psalm.dev/
{{References}}
[[Category:Tools]]
