Religious Anti-Realism and Engineering Temperament

Why does the engineering mindset gravitate toward religious anti-realism?

Engineering trains the mind to demand testable claims, reproducible evidence, and falsifiable hypotheses, none of which religious metaphysics can provide in the empirical register that engineers inhabit professionally.

The professional habits of the engineer are empiricist habits. You write a test and it passes or fails. You deploy code and it works or crashes. You measure latency and it is 47 milliseconds or it is not. Every day, in every technical decision, the engineer operates within a framework where claims are tested against observable reality and revised or discarded based on evidence.

Carry this framework into questions of theology and the conclusion feels almost inevitable. There is no A/B test for the existence of God. There is no reproducible experiment for the soul. The resurrection does not have a postmortem with a root-cause analysis. The engineer’s toolset, which is excellent for production systems, returns null when applied to metaphysical claims.

I arrived at religious anti-realism through this path. By 28, I had spent a decade training my mind to demand evidence for every claim. When I turned that demand toward the religious beliefs I inherited, they could not meet it. The process felt clean and logical. It took me another decade to realize it was also incomplete.

What does intellectual honesty demand at the boundary of empiricism?

Intellectual honesty demands acknowledging that the absence of empirical evidence for a claim is not the same as evidence for its absence, and that empiricism itself rests on assumptions it cannot empirically justify.

The engineer who says “I only believe what can be empirically verified” is making a statement that cannot itself be empirically verified. The claim is self-referentially incoherent. This is not a gotcha. It is a genuine philosophical problem that empiricists from Hume to Quine have wrestled with. The scientific method is extraordinarily powerful, but it cannot justify its own foundations. The uniformity of nature (tomorrow will resemble today) is an assumption, not a finding. The reliability of induction is trusted, not proven.

Wittgenstein captured this with characteristic precision: “Whereof one cannot speak, thereof one must be silent.” The sentence is usually read as a dismissal of metaphysics. It can equally be read as a statement of intellectual humility: the limits of my language are the limits of my world, and the limits of empiricism are the limits of empirical inquiry, not the limits of reality.

“The most beautiful thing we can experience is the mysterious. It is the source of all true art and science.” — Albert Einstein, 1930

What are the distinct positions available to the intellectually honest engineer?

The honest engineer can hold one of several defensible positions: strong atheism (no gods exist), weak atheism (I lack belief in gods), agnosticism (the question is undecidable), or what I call “empirical silence” (the question is outside my toolkit and I will not pretend otherwise).

• Strong atheism: Claims that God does not exist. This is a positive metaphysical claim that requires its own justification, not merely the absence of evidence for theism. Few philosophers of religion find it defensible without additional argument.
• Weak atheism/agnosticism: Lacks belief in God without claiming certainty about non-existence. This is the most epistemically modest position and the one most consistent with engineering empiricism: “I have not encountered sufficient evidence, and I withhold belief.”
• Religious non-cognitivism: Holds that religious statements are neither true nor false because they do not express propositions. “God is love” is not a claim about reality but an expression of value, like “kindness matters.” This position, associated with A.J. Ayer and the logical positivists, has the elegance of a well-refactored codebase but may oversimplify.
• Empirical silence: Acknowledges that empiricism is the right tool for empirical questions and the wrong tool for metaphysical ones, and refuses to extend it beyond its domain. This is the position I have settled into: not because I lack opinions, but because extending empiricism into metaphysics is the same category error as using a thermometer to measure happiness.

How does this connect to the practice of engineering?

The same epistemic humility that makes a good engineer (knowing the limits of your tools) should apply to the question of God: recognizing that your empirical toolkit has a scope, and that scope does not encompass all questions worth asking.

I have watched brilliant engineers make the same error in metaphysics that junior developers make in architecture: applying a tool they know well to a problem it was not designed for, and then blaming the problem when the tool fails. The junior developer uses a relational database for a graph problem and concludes that the data is bad. The engineer uses empiricism for a metaphysical question and concludes that the question is bad.

The question may indeed be bad. Some philosophers, following the logical positivists, argue that metaphysical questions are meaningless because they cannot be empirically answered. But “meaningless to my methodology” is not the same as “meaningless.” The question of whether consciousness is reducible to physical processes is not empirically resolvable with current tools, yet no serious person would call it meaningless.

What I have found is that the engineers who hold their anti-realism lightly, who say “I do not believe, but I acknowledge the limits of my framework,” are also the engineers who hold their architectural opinions lightly. Epistemic humility is not domain-specific. It is a character trait. The engineer who says “I am certain there is no God” with the same tone they say “I am certain PostgreSQL is better than MySQL” is displaying the same rigidity in both domains.

Where does the engineer go from here?

The engineer goes toward honest inquiry: reading the strongest arguments on all sides, acknowledging uncertainty without performing certainty, and accepting that some questions may remain permanently open.

I keep 4 books on my desk that represent positions I do not hold. Thomas Aquinas’s Summa Theologica. Sam Harris’s The End of Faith. Karen Armstrong’s The Case for God. Thomas Nagel’s Mind and Cosmos. Each argues a position I find partially compelling and partially inadequate. The point of keeping them is not to find the answer. It is to resist the engineer’s temptation: the belief that every question has a solution, and that the absence of a solution means the question is defective.

Some questions are not bugs to be fixed. They are features of the human condition, permanently open, permanently uncomfortable, permanently worth sitting with. The engineering temperament will always prefer the testable to the mysterious. The question is whether it can hold both without collapsing one into the other.

I do not know whether God exists. I do not know whether the question is well-formed. I know that empiricism is the best tool I have for understanding the physical world, and I know it is not the only world there is to understand. That admission costs me nothing in my engineering practice and gains me something in my intellectual life: the honesty to say that my best tools have boundaries, and that the territory beyond those boundaries is not nothing simply because my instruments cannot map it.