Clarke's third law
expressionops culture
'Any sufficiently advanced technology is indistinguishable from magic.'
Arthur C. Clarke's third law was written about prophecy and progress, but engineering adopted it as a diagnosis: when users, or engineers, cannot see the mechanism, they reason about the system with superstition instead of models. That is where cargo-cult fixes, ritual reboots, and 'it works, don't touch it' come from. The working corollary for practitioners: any technology distinguishable from magic is insufficiently advanced, and any team treating its own stack as magic is insufficiently informed.
Any sufficiently advanced technology is indistinguishable from magic. Arthur C. Clarke's formulation is usually quoted admiringly, and it is worth reading as a warning as well, because the state it describes is one where users cannot reason about a system at all.
The practical version appears constantly in support work. A user who cannot distinguish a network problem from an application problem from a device problem is in exactly the position Clarke described, and their model of the system is therefore ritual: this sequence of actions worked last time. That is not ignorance, it is the rational response to a system that offers no visible causality, and it makes accurate reporting impossible.
Which suggests a design obligation rather than a boast. Systems that expose some legible model of what they are doing, error messages that describe the actual condition, and interfaces whose behaviour can be predicted from a simple mental model all reduce the magic. That matters most in security, since a person who cannot tell normal from abnormal has no chance of noticing an attack, and the industry has spent a great deal of effort making its systems more magical rather than less.