$500.00 Bounty for Idea #3069Beta

@dennis-hackethal wants more criticisms of this idea. The bounty will be prorated among critics based on the number of eligible criticisms. Submissions end on .

Idea to criticize

My critique of David Deutsch’s The Beginning of Infinity as a programmer. In short, his ‘hard to vary’ criterion at the core of his epistemology is fatally underspecified and impossible to apply.

Deutsch says that one should adopt explanations based on how hard they are to change without impacting their ability to explain what they claim to explain. The hardest-to-change explanation is the best and should be adopted. But he doesn’t say how to figure out which is hardest to change.

A decision-making method is a computational task. He says you haven’t understood a computational task if you can’t program it. He can’t program the steps for finding out how ‘hard to vary’ an explanation is, if only because those steps are underspecified. There are too many open questions.

So by his own yardstick, he hasn’t understood his epistemology.

You will find that and many more criticisms here: https://blog.dennishackethal.com/posts/hard-to-vary-or-hardly-usable

#3069·Dennis HackethalOP revised about 1 month ago

Terms

Read the linked blog post at https://blog.dennishackethal.com/posts/hard-to-vary-or-hardly-usable in its entirety. Focus on Deutsch’s epistemology of hard and easy to vary.

I want to be proven wrong about Deutsch’s epistemology.

Eligible submissions must meet all of the following conditions:

  • Demonstrate a thorough understanding of the relevant parts of my blog post (the parts criticizing Deutsch’s epistemology). Include a summary in your own words.
  • Submit a working program implementing Deutsch’s epistemology in code. It must:
    • Accept two strings representing arbitrary explanations in natural language (English).
    • Return a ranking indicating which explanation is better, worse, or equal.
    • Be rigorous, sufficiently specified, non-arbitrary, and meet industry standards for code reviews.
    • Be fully testable – something I can paste into a console and run with various explanations.
  • Submissions must be handwritten. No AI-generated text or code; suspected AI use makes submissions ineligible.
  • Any major programming language is acceptable (e.g., Ruby or JavaScript); avoid esoteric or niche languages.

Remember to mark your submissions as criticisms.

Site-wide terms apply. To be eligible for a payout, participants must, at the time the bounty ends, have connected a Stripe account in good standing and submitted at least one direct criticism of idea #3069 meeting all bounty terms and having no pending counter-criticisms. Counter-criticisms do not need to meet the bounty terms.

To participate, sign up or log in.

Timeline

Bounty startReview end
In progress
The bounty starts. Participants submit criticisms.
Submissions end. @dennis-hackethal reviews them.
The review period ends. Eligible critics receive prorated shares of the bounty.