David Deutsch - What is Truth?

Mike's Notes

This video interview came in the latest issue of Aeon.

Resources

References

  • Reference

Repository

  • Home > Ajabbi Research > Library > Subscriptions > Aeon
  • Home > Ajabbi Research > Library > Subscriptions > Closer to Truth
  • Home > Handbook > Ajabbi Research > Culture

Last Updated

02/07/2025

David Deutsch - What is Truth?
By: Lawrence Kuhn
Closer to Truth: 18/10/2016

David Elieser Deutsch, FRS is a British physicist at the University of Oxford. He is a Visiting Professor in the Department of Atomic and Laser Physics at the Centre for Quantum Computation (CQC) in the Clarendon Laboratory of the University of Oxford.

Deutsch pioneered the field of quantum computation by formulating a description for a quantum Turing machine, as well as specifying an algorithm designed to run on a quantum computer. He is a proponent of the many-worlds interpretation of quantum mechanics.

He was awarded the Dirac Medal and Prize of the International Centre for Theoretical Physics in 2017, the Isaac Newton Medal and Prize of the Institute of Physics in 2021, and the Breakthrough Prize in Fundamental Physics in 2022. His popular books The Fabric of Reality and The Beginning of Infinity have each been translated into 12 languages.

Why David Deutsch believes good explanations are the antidote to bad philosophy

In this interview from the long-running series Closer to Truth, the British theoretical physicist and philosopher David Deutsch makes the case that understanding the difference between good and bad explanations is central to advancing knowledge. In conversation with the US presenter Robert Lawrence Kuhn, Deutsch outlines what he believes makes for a convincing explanation – primarily, unprejudiced thinking, relevance and specificity. Further, he argues that this framework for explanations is a vital corrective to a century in which what he calls ‘bad philosophy’, including logical positivism, has dominated, constraining the search for good ideas.

Thinking about the next steps ahead

Mike's Notes

I had the regular meeting on Sunday night, which helped bounce ideas around. I would like to know what people think of what I have written. Just contact me for a chat.

Resources

References

  • Reference

Repository

  • Home > Ajabbi Research > Library >
  • Home > Handbook > 

Last Updated

01/07/2025

Thinking about the next steps ahead

By: Mike Peters
On a Sandy Beach: 01/07/2025

Mike is the inventor and architect of Pipi and the founder of Ajabbi.

Ajabbi uses Pipi 9 to run on, known as "dogfooding". Steady progress is being made with Pipi 9, and the first customer website, which is now well underway.

The customer's website required several reusable modules and utilises these engines and more.

  • Website Engine
  • Reference Engine
  • i18n Engine
  • Reference Engine

Documentation of these modules and engines is now required for developers and administrators.

Next Project

It was now time to determine a plan for the next project.

There are three options;

  • Finish the developer documentation
  • Complete the user workspace roadmap
  • Build a simple SaaS application

I will go into some detail about each option.

Finish the developer documentation.

No developer will be able to build anything with Pipi unless they have some documentation on how it works. 5% is documented.

Complete the user workspace roadmap.

This will enable users to log in and use the available features, but they will still require instructions in the form of documentation.

Build a simple SaaS application.

The Movie Industry SaaS application is straightforward and utilises a compact ontology. Its ontology is over 1,000 times smaller than SNOMED, so it's an easy place to start. It would be a way to test the Ontology API and Boro engines. It builds some more reusable modules. It also provides a helpful tool that people can use for their work.

This would generate more learning opportunities for me, as I do this work by the seat of my pants.

Discussion

The advantage of building a simple SaaS application is that it requires a user workspace and some relevant documentation. 

Being product-led, would only schedule work on any necessary background systems and documentation. It also makes things more manageable as Pipi slowly scales.

Over time, more modules will be completed, more engines will be documented, and the user workspace will expand.

Show and tell

Embedding short YouTube video recordings demonstrating workspace usage could be incorporated into training and contextual help documentation.

A longer, prerecorded technical demonstration video, accompanied by slides and a PDF white paper, could then be shared with the Ontolog Forum to solicit critical feedback. I suspect they would be curious about a novel use of Ontology technology as part of constraints in State Space.