Hanlon's Razor

Hanlon’s Razor advises against assuming bad faith when an outcome may be due to human error or ignorance. If a commit introduces a security hole, it’s probably a mistake, not intentional sabotage. So one responds with help and fixes, not with blame.

This doesn’t mean ignoring the possibility of malice when truly warranted (security does consider malicious actors). But for day-to-day development and operations, Hanlon’s Razor keeps you grounded: the build failed likely due to a misconfiguration, not because someone deliberately broke it.

• When something goes wrong, it's likely not malicious but rather an error or misunderstanding.
• Don't jump to 'the system is hacked' or 'someone intentionally broke this.' First, consider simpler explanations (e.g., a configuration file was missed or a typographical error).
• If a colleague's code is problematic, it's probably not sabotage. It may be due to being rushed or unaware of something. Try to approach with questions, not accusations.