Paracelsus Maxim applied to programming warns that context and dosage determine tool utility

The Paracelsus Maxim, originally a toxicology principle, is repurposed here to critique absolutist thinking in software engineering. Fowler highlights that practices like using global data are not inherently flawed but become problematic when misapplied or overused. This reframes debates about best practices by shifting focus from rigid rules to situational awareness.

The analogy extends beyond global data to other contentious patterns in software design. For example, microservices or monoliths, static typing or dynamic languages, and even testing strategies all exhibit trade-offs that depend on dosage and context. A small team might benefit from the simplicity of a monolith, while a large organization could struggle with its scaling limitations. The maxim serves as a reminder to evaluate tools based on their fit for the problem at hand.

This perspective also challenges the tendency to adopt practices based on popularity or dogma. Engineers often default to patterns they’ve seen succeed elsewhere without considering whether the dosage or context aligns with their own projects. The Paracelsus Maxim encourages a more deliberate approach: testing assumptions, measuring impact, and adjusting usage rather than treating practices as one-size-fits-all solutions.

However, the maxim’s applicability has limits. Some practices, like memory leaks or unhandled exceptions, are almost always harmful regardless of dosage. The principle works best for tools or patterns that occupy a gray area, useful in moderation but dangerous when overused. It also doesn’t eliminate the need for judgment; determining the right dosage for a given context still requires experience and experimentation.