The Certainty Trap: How Cultures Construct Absolute Truth in a World Where None Exists

Here’s the fundamental paradox of human existence: we desperately need definitive answers in a reality where no such answers could ever exist. We crave certainty about ultimate questions—the nature of reality, the purpose of existence, the right way to live—but we inhabit a world where objectivity is not just difficult to achieve but conceptually impossible. Knowledge requires a knower, and knowers are always situated somewhere, with particular perspectives that shape everything they can understand.

This creates one of the most fascinating phenomena in human culture: entire societies that construct elaborate systems for generating absolute certainty about questions that have no absolute answers. In cultures steeped in religious tradition, you’ll encounter something remarkable: people who speak with unwavering conviction about ultimate truths. They don’t hedge, qualify, or express doubt about moral reality, divine purpose, or the fundamental structure of existence. They know—with the kind of definitiveness that makes secular observers squirm—exactly what is true and what is false.

But here’s what makes this phenomenon so philosophically unsettling: there is no objective truth for them to be certain about. No view from nowhere. No neutral ground. No ultimate perspective that transcends human situatedness. The definitive answers that these cultures provide with such confidence are constructions—sophisticated, socially reinforced, emotionally satisfying constructions—but constructions nonetheless. They’re understandable responses to a genuinely impossible situation—the human need for definitive answers in a reality where no such answers could ever exist.

The Architecture of Absolute Conviction

Religious societies don’t just stumble into certainty. They build elaborate systems to generate and maintain it. Sacred texts become unquestionable sources of truth rather than historical documents written by particular people in particular contexts. Theological interpretations crystallise into doctrine. Community practices reinforce shared perspectives until they feel like natural facts rather than cultural agreements.

But you don’t need traditional religion to see this pattern. Consider the Agile software development community—a thoroughly secular, technical culture that exhibits all the hallmarks of faith-based certainty. They have their sacred text (the Agile Manifesto), their prophets (Kent Beck, Martin Fowler), their orthodoxies and heresies, their ritualistic practices (daily standups, retrospectives, sprint planning), and most importantly, their unshakeable conviction that they’ve discovered the fundamentally one true way to build software.

Watch how this works in practice. An Agile advocate doesn’t say ‘our particular approach to software development, based on our interpretation of certain principles within our cultural context, seems to work well for many types of projects.’ They say ‘Agile is how software should be built.’ The perspectival nature of their knowledge—the fact that it emerged from specific people solving specific problems in specific contexts—gets erased through confident proclamation about universal principles.

This isn’t accidental. Religious systems are remarkably effective at transforming situated, culturally constructed viewpoints into what feel like universal, eternal truths. The community member experiences their beliefs not as one possible way of organising reality amongst many, but as reality itself.

The Social Construction of the Sacred

What makes religious certainty so powerful is precisely what makes it so philosophically problematic: it’s deeply social. When your family, neighbours, spiritual leaders, and intellectual authorities all share the same fundamental picture of reality—when that picture gets reinforced daily through ritual, story, and communal practice—it gains a solidity that individual reflection could never achieve.

The Agile community demonstrates how this works in secular contexts. Attend any Agile conference, join any Scrum team, participate in any DevOps initiative, and you’ll find yourself immersed in a culture where certain beliefs are simply givens. Everyone knows that cross-functional teams are better than specialised roles. Everyone agrees that working software matters more than comprehensive documentation. Everyone understands that responding to change trumps following a plan. These aren’t treated as contextual preferences or cultural choices—they’re treated as discovered truths about the nature of effective software development.

But this social reinforcement doesn’t make the beliefs more objectively true. It just makes them feel more true. The Agile practitioner’s confidence comes not from having transcended perspective but from being so thoroughly embedded in a particular perspective that alternatives become literally unthinkable. When your entire professional network speaks the same language, attends the same conferences, reads the same thought leaders, and practises the same rituals, dissenting views don’t just seem wrong—they seem apostatic.

Consider how religious communities handle doubt or alternative viewpoints. They’re not typically engaged as legitimate challenges to explore but as temptations to resist, errors to correct, or signs of spiritual weakness. The system is designed to maintain certainty, not to test it against the possibility that no ultimate certainty exists.

The Agile community exhibits identical patterns. Suggest that some projects might benefit from more upfront planning and comprehensive documentation, and you’ll be met not with curious inquiry but with correction about why you ‘don’t understand’ Agile principles. Point out that specialised roles might be more effective than cross-functional teams for certain types of complex work, and you’ll be dismissed as having ‘waterfall thinking.’ Question whether two-week sprints are optimal for all types of development, and you’ll be told you’re ‘not doing Agile right.’ The community has developed sophisticated mechanisms for deflecting challenges to its core certainties whilst maintaining the illusion of being empirically driven and pragmatic.

The Neuroscience of Constructed Truth

Modern brain research reveals just how thoroughly our minds construct rather than simply receive reality. We don’t perceive the world and then add interpretation—perception itself is interpretation, shaped by expectations, prior beliefs, and cultural training. Our brains are constantly filling in gaps, making predictions, and filtering information according to existing frameworks.

Religious cultures provide incredibly powerful frameworks for this interpretive process. They offer comprehensive stories about the nature of reality, clear categories for organising experience, and strong emotional investments in particular ways of seeing. These frameworks become so fundamental to how believers process information that contradictory evidence gets filtered out, reinterpreted, or simply not perceived at all.

The result is experiential certainty about truths that exist only within the interpretive system that generates them. The believer doesn’t feel like they’re constructing truth—they feel like they’re discovering it. But the ‘discovery’ is actually the successful operation of a meaning-making system that transforms cultural artefacts into felt reality.

The Paradox of Revealed Truth

Religious systems solve the problem of epistemic uncertainty through claims to revealed truth. God, they assert, has provided direct access to ultimate reality through scripture, prophecy, or mystical experience. This revelation supposedly transcends the limitations of human perspective, offering the view from somewhere that secular knowledge cannot achieve.

The Agile community has created its own version of revealed truth through the Agile Manifesto—a document that’s treated not as one group’s opinions about software development circa 2001, but as a timeless discovery of fundamental principles. The seventeen signatories aren’t presented as particular individuals with particular backgrounds solving particular problems in particular contexts. They’re treated as visionaries who uncovered universal truths about how software should be built. How lame is that?

But both religious revelation and Agile principles come through thoroughly human channels—particular people, in particular cultural contexts, with particular assumptions, beliefs and interests. Even if we granted that the Agile founders had genuine insights about software development, we’d still be left with thoroughly human processes of interpreting and applying those insights across radically different contexts, organisations, and problem domains.

Agile communities hardly ever acknowledge this. Instead, they treat their particular interpretations of the manifesto as having the same authority as the original principles themselves. A Scrum Master’s understanding of ‘individuals and interactions over processes and tools’ becomes indistinguishable from what the principle was conceived to mean. The interpretive community’s practices become the authentic expression of Agile truth itself.

The Comfort of False Certainty

Why do religious cultures cling so tenaciously to definitive answers when no such answers actually exist? Because uncertainty is existentially difficult. The human condition involves navigating fundamental questions about meaning, morality, and purpose without access to ultimate truth about any of them. We’re thrown into existence, forced to make choices, compelled to find meaning, all whilst standing on epistemological quicksand.

The same psychological need operates in professional contexts. Software development is inherently uncertain—complex problems, changing requirements, unpredictable technical challenges, human coordination difficulties. The Agile community offers firm methodological ground where none actually exists. They provide clear answers to unanswerable questions about the ‘right’ way to organise teams, plan projects, and deliver software. The psychological relief this provides is enormous—so enormous that practitioners often can’t imagine giving it up, even when presented with compelling evidence that Agile practices don’t work well in their specific context.

There’s a deeper dynamic at work here, one that science fiction captured perfectly in the later Stargate series. The Ori gained literal power from the belief of their followers—the more people believed in Origin, the more powerful the Ori became. Whilst this is fiction, it points to a real phenomenon: belief systems gain tremendous social and psychological power precisely through the intensity of conviction they generate. The certainty itself becomes the source of the system’s authority, independent of whether its foundational claims correspond to any notional reality.

This isn’t intellectual dishonesty so much as human necessity. Most people cannot work comfortably with the full implications of methodological uncertainty. Agile culture provides elaborate mechanisms for avoiding that discomfort through the construction of false but emotionally sustainable certainties about software development best practices.

The Price of Constructed Truth

The problem with building identity and community around definitive truths that don’t actually exist is rigidity. When your fundamental understanding of reality depends on maintaining particular beliefs, those beliefs become non-negotiable. Alternative perspectives aren’t just different—they’re threatening to the entire system of meaning that makes life livable.

This creates the characteristic inflexibility that secular observers find so frustrating in religious discourse. It’s not that religious believers are naturally more dogmatic than other people. It’s that their entire framework for understanding reality depends on treating constructed certainties as ultimate truths. Acknowledging the perspectival, contingent nature of their beliefs would undermine the very certainty that makes the beliefs psychologically valuable.

Religious cultures often respond to challenges by doubling down rather than engaging seriously with alternatives. This makes perfect sense within their own logic—if you’ve organised your entire worldview around the premise that certain truths are absolute and eternal, then treating them as open questions becomes impossible.

The Impossibility Runs Deeper

Could there be any conceivable world where objectivity actually exists? Perhaps a reality where minds work like perfect recording devices rather than active interpreters? But even then, someone would need to decide what to record, how to organise the recordings, and what counts as relevant—which reintroduces perspective.

Maybe a world where all conscious beings share identical conceptual frameworks, languages, and ways of organising experience? But this just pushes the problem back one level. Why these particular shared categories rather than others? The choice of universal framework would itself reflect a particular perspective.

What about some form of mystical direct access that bypasses all interpretation? ‘Direct access’ still requires someone to have the access, and that someone would need ways of understanding and communicating what they’ve accessed—which brings us back to perspective and interpretation.

Even the fantasy of accessing a God’s-eye view doesn’t solve the problem. An omniscient divine perspective would still be a perspective. An infinite being would still have to choose what to attend to, how to organise infinite information, what to consider relevant. Those choices would reflect the particular nature of that divine consciousness.

The deeper truth is that objectivity isn’t just contingently impossible in our world—it’s conceptually impossible in any world with conscious beings. Knowledge requires a knower, and knowers are always situated somewhere, with particular capacities, assumptions, beliefs, interests, and ways of organising experience. The very concept of ‘perspective-free knowledge’ is as oxymoronic as ‘married bachelor’—not just empirically unavailable but logically contradictory.

This means the certainty-construction systems we see in religious cultures, Agile communities, and countless other belief systems aren’t flawed responses to a solvable problem. They’re understandable responses to a genuinely impossible situation—the human need for definitive answers in a reality where no such answers could ever exist.

What They’re Really Forgetting

The confidence they feel comes not from having transcended human limitations but from having found particularly effective ways of forgetting about them. But what exactly are these sophisticated forgetting systems helping people avoid confronting?

It’s fundamentally the groundlessness of everything. As the old saying goes, ‘It’s turtles all the way down.’

The reference is to a classic philosophical joke: a philosopher explains that the world rests on the back of a giant turtle. When asked what the turtle stands on, he replies ‘another turtle.’ And what does that turtle stand on? ‘It’s turtles all the way down.’

This captures the infinite regress problem that makes human knowledge so psychologically difficult. Every belief, every foundation, every supposedly solid principle rests on other beliefs, other foundations, other principles—with no final turtle at the bottom holding it all up. When you ask what any system of knowledge ultimately rests on, you find it’s turtles all the way down.

Religious and ideological certainty-construction systems are elaborate ways of convincing people that their turtle is the bottom one. That their foundational texts, principles, or revelations aren’t just more turtles but actual bedrock. The Agile community does this by treating the Manifesto as discovered truth about software development rather than just another turtle—one group’s opinions from 2001 sitting on more turtles of their particular experiences, cultural context, and assumptions and beliefs about work and technology.

Religious communities do it by treating their scriptures as divine revelation rather than human documents sitting on more layers of human interpretation, translation, cultural transmission, and historical contingency.

The psychological genius of these systems is helping people stop looking down at the infinite turtle stack. They provide what feels like solid ground to stand on, when the actual situation is turtles all the way down. The confidence comes from successfully forgetting about the turtle stack underneath their particular turtle.

Living in the Gap

The tension between religious certainty and philosophical reality creates a fascinating cultural phenomenon: entire societies organised around definitive answers to questions that have no definitive answers. These societies produce people who can speak with absolute confidence about the nature of God, the purpose of existence, and the structure of moral reality, even though no such absolute knowledge is available to finite, situated, culturally embedded human beings.

This doesn’t make religious cultures less sophisticated than secular ones—secular cultures have their own ways of avoiding full confrontation with epistemic uncertainty. But it does reveal something important about human psychology: our profound need for certainty often overrides our capacity for acknowledging the limits of human knowledge.

Religious believers aren’t wrong to want definitive answers to ultimate questions. They’re wrong to think they have them. The certainty they experience is real, but it’s the certainty of successful meaning-construction, not the certainty of correspondence with objective truth. The confidence they feel comes not from having transcended human limitations but from having found particularly effective ways of forgetting about them.

In a world where objectivity is impossible and truth is always constructed from particular perspectives, both religious and secular communities represent the same strategy for dealing with this uncomfortable reality: build robust systems for generating false but livable certainties, then protect those certainties by treating them as immune to the very philosophical insights that reveal their constructed nature.

The Agile community perfectly illustrates this pattern. It’s created a comprehensive belief system around software development that provides definitive answers to inherently uncertain questions. It’s built social structures to reinforce these beliefs, developed rituals to embody them, and created mechanisms to deflect challenges to them. Most importantly, it’s convinced itself that its particular cultural artefacts represent discovered truths about the objective nature of effective software development.

It’s an understandable response to an impossible situation. But the Agile comminity is responding to something that doesn’t exist—absolute answers to questions that don’t have absolute answers. The definitive views that characterise both religious cultures and Agile communities aren’t discoveries about reality. They’re successful systems for burying uncertainty, mistaken for the certainty itself.

Further Reading

Beck, K., Beedle, M., van Bennekum, A., Cockburn, A., Cunningham, W., Fowler, M., … & Thomas, D. (2001). Manifesto for agile software development. Retrieved from https://agilemanifesto.org/

Feyerabend, P. (1975). Against method: Outline of an anarchistic theory of knowledge. New Left Books.

Nagel, T. (1986). The view from nowhere. Oxford University Press.

Pratchett, T. (1988). Small gods. Gollancz.

Related Works:

Berger, P. L., & Luckmann, T. (1966). The social construction of reality: A treatise in the sociology of knowledge. Anchor Books.

Kuhn, T. S. (1962). The structure of scientific revolutions. University of Chicago Press.

Rorty, R. (1979). Philosophy and the mirror of nature. Princeton University Press.

Wittgenstein, L. (1953). Philosophical investigations. Blackwell.