Friday, December 21, 2018

The still-relevant bits of this blog - an overview, 2003-2018

I've used this blog to jot down thoughts and ideas, which I sometimes want to go over. But by this point it contains so much content that it's hard for me to dive into it. This post is an attempt to provide a quick overview of its content, that: filters out posts that are no longer relevant for me, tries to organise the material into logical groupings, and summarises the basic point of each post.

On the topic of my thoughts and ideas, there's also what I've written on Hacker News, Reddit, Twitter, and Quora.

Basic Research

What is the value of basic research? Not individual pieces of basic research, but that entire category of research? My thoughts on how we can think about this question, and why basic research's value is significantly underestimated.

Scientific and Technological Development

It is useful to see scientific and technological development as removing constraints on our ability to achieve goals. This demystifies this process, and suggests possible future developments.

Information Ecosystem

The information ecosystem is all the means, across all of society, of storing, presenting, communicating, and using information. In that, how can we help truths to spread and hinder the spread of falsehoods? (one idea this post contains is a source outlining more applied kinds of mistaken reasoning and justification).

Thoughts on how we can use fact checking, and linking to supporting evidence, to help improve the information ecosystem. A goal being to make 'providing supporting evidence' more of a norm. And some thoughts on how we can make fact checking practical and as easy as possible.

An authoritative source of current scientific opinion would help. A source for reliable statistics for facts like "X% of working biologists believe in the theory of evolution". It'd be an important resource for informing the public and those making social policies.

Bret Taylor's suggestion for a Wikipedia for data (statistics, listings, etc), which still doesn't seem to have come to fruition.

A few minor things. Identifiers for news topics would help. If a topic (like a particular accident that occurred) could be given a unique identifier, and if all reporting and follow-ups on it (by all different parties) referenced that identifier. Some articles suggesting improvements to news sites. Some sites for structured representations of debates on topics (though it is questionable how much value these have): Debatepediaspacedebate.org (which uses the Open Debate Engine, as do these two).

Related: Clay Shirky on the use of evidence in society (his response to the 2007 Edge question). He explains why "even today, evidence has barely begun to upend authority", and why, despite this, he's optimistic this is changing.

Interactive Storytelling

Can we use interactivity not for player agency, but as a means of increasing their immersion in a character's perspective? Think of something more like an interactive movie or documentary than a game. I sketch a high-level vision for this.

Some ideas for how we could use interactive storytelling teach skills like communication skills.

Minor:

A miscellaneous idea: could you use a character like a Nintendog in narrative-focused game?

(And not something I intend to pursue, but a thought on presenting stories through email correspondence. Including the idea of seeing the emails drafted in real-time.)

Though not necessarily something you'd use for interactive storytelling, here's a concept you could use in a computer game: to graphically represent a character's (like the one the player is controlling) perceptual attention. Not the area they're looking at, but the differing levels of attention they're giving to things within that area.


Cognitive

Tropes in fictional TV and movies that propagate inaccurate, damaging views. Tropes such as 'grief is always overt',  'attractiveness correlates with character', and 'intelligence is Spock-like'.

'Core world-model' as a Creole

(I'm not happy with how I described this in the original post, so the following overview puts it in different terms). Core world-model as a creole (original post titled "Knowledge as a creole"). Creoles are a type of spoken language, and they way they come about shows us that children build their understanding of a language according to an unconscious, structured process that integrates available linguistic details from their environment. I argue that we build our 'core model of the world' in a similar fashion. And like with language learning, it's difficult to modify this or integrate new details once a person is an adult. Many 'paradigm shifts' could be explained, in this view, as a result of the first generation growing up such that new insights are able to be integrated in such a fashion into their 'core model of the world'.

Related to this, Clay Shirky argues that a lack of knowledge is useful for entrepreneurs.

Poor language/concept use

Minor:

Cases where words have been adapted for use in a new context, where their original meanings are misleading in the new context. "Stretching" muscles, and radio-signal "interference".

"Analog" properties, such as the level of mercury on a thermometer, are really those whose levels can change in increments smaller than we can perceive.

Treating the meaning of some words/phrase in terms of their meaning in the abstract can cause confusion. We need to think of what their meaning is in the particular context in question. Another example of this.

Popper's "What is Dialectic?" is an excellent example the interaction between language and thought and the problems that can be thus caused.


Species, Language and Reality: an example of how language misleads us. The notion of 'species' makes it seem like there's a lack of 'intermediate forms' in fossil records, where there's no actual such issue. (Also related to the 'evolution' topic found below).

Opinions Aren't Always Just Opinions: arguing against common view that opinions are unquestionable.

Phrasing and significance: some simple examples of where language is used to make something sound significant.

Label it terrorism, do what you like: a brief post on how labelling things can make readers jump straight to emotional reactions and conclusions, skipping the step of checking whether the label is apt.


Thinking

Minor:

I had a lot of difficulty summarising the following post, and I ended up mostly re-writing it in my attempt. The original also provides a potential explanation of why we tend to overlook the negative processes.
I think critical thinking is probably a lot more important than obtaining knowledge. Not that the latter is unimportant, but that a strong core of critical thinking is necessary, along with obtaining knowledge, for good results. 
Knowledge and intelligence can be structures/processes that reflect how things are, so increase our knowledge and intelligence by obtaining more of these things (through reading, practice, etc). That is, they can be 'positive' things. But they can also be 'negative'. Critical thinking. Knowledge and intelligence that enables us to be critical, to not jump to conclusions, to not overgeneralise, to critically evaluate inferences. These negative elements are filters, they're avoid avoiding inaccurate knowledge/reasoning.
It's important to apply such filters. Many ideas come from intuition, and intuition doesn't work very well for many topics (e.g. science, technology and economics). We tend to get knowledge from what we hear/learn from others -- building new knowledge is very difficult and time-consuming -- and there's many inaccurate views out there (e.g. views that aren't accurate but are good at propagating amongst the population). There's many more ways to be wrong than to be right, and once a false view gets into your brain it can be difficult to dislodge.
Positive learning/practice can contribute to being critical, but it doesn't necessarily lead to that, and a critical attitude is somewhat of a parallel track that gets benefits aside from positive learning.
We tend to think that if we can't see how our understanding can be improved, that this is because it can't be. But the fact that we can't see how it can be improved is not because it can't, but because of the limitations of our ability to imagine such details. Basically, if we could see how our understanding could be improved, we'd already have that improved understanding. (This is an example of the generally positivist character of intuitive thinking).

A purely-speculative notion is one without any supporting evidence. When a purely-speculative notion is invoked to explain some phenomenon, it's less obvious that it's purely-speculative. Think of pre-scientific explanations of the natural world, like the spheres many believed to be associated with epicycles. The fact that it's doing explanatory work makes it seem more real, and there is something of it being nested within an explanation that makes it more difficult to take a critical eye to. Such purely-speculative notions may even become a transparent part of how we perceive/conceptualise the phenomenon, such that the fact of the phenomenon's existence and character seems to provide concrete evidence of the existence of the -- in fact, purely speculative -- phenomenon.
In a subsequent post I clarified a couple of things. What I mean by evidence: if an explanation turns out to be false we can see there was never any actual evidence for it, just information that was suggestive to us, that we incorrectly took as evidence. Some explanations really are purely-speculative: they're just-so stories that only have going for them that if they were true then they would provide an explanation. And, that purely-speculative explanations aren't intrinsically bad. They are a necessary part of theorising and obtaining a true explanation. They're bad when the lack of associated evidence isn't recognised.
In a further post, I distinguished between a potential explanation (that demonstrates nothing more than a potential, and neither indicates that it is the explanation nor rules out other potential explanations), and an actual explanation (that demonstrates that this, out of all the possible explanations, is the actual explanation of the phenomenon). No amount of potential explanation evidence can demonstrate that something is the actual explanation. The inability to imagine an alternative explanation is often cited as evidence that a potential explanation must be the actual explanation, but it does not provide any evidence for this.
When we draw a conclusion about X (an item, a situation, etc) we should do so by looking at the properties of X that are relevant to whether that conclusion holds or not. It is, however, very easy to take lazy shortcuts --- to jump to conclusions -- and draw that conclusion based on generalisations that apply to X rather than actually looking at the particulars of X. This is an example of that.

Instead of judging whether something is plausible by trying to imagine whether it could exist (the flaw in this is that positivist attitude), we should try to find reasons why it couldn't exist -- and if we can't, be agnostic about whether it could exist or not. If you need to take some action action that's dependent upon whether the thing exists or not, that action needs to go one way or the other, but even this doesn't require you to have a definitive belief.


A benefit of learning to program. There's times when you think you understand something, but in fact you don't really.  Programming makes you better at spotting such cases, and I think can help your ability to spot such cases outside of programming as well.

There's a strong tendency to assume psychological cases for medical conditions. Some examples. Duodenal ulcers used to be blamed on psychological factorsAs was scurvy (which was also blamed on environmental factors).

Wikipedia's list of common misconceptions (direct link).


Missing the thickets for the forest. Focus too much on the trees and you can miss the forest. But focus too much on the forest and you can miss the intermediate structures -- patterns or structures within the whole -- the thickets.

Fact memorisation supplants thinking. A focus on learning lightweight facts, which give you rote instructions (like the 'tips' that lifestyle shows tend to focus on), hinders ones ability to think about a situation.

Short Michael Shermer article on relativism. "Wronger Than Wrong: Not all wrong theories are equal" (direct link).

In demonstrating or evaluating an argument, we tend to focus on the reasoning between the premises and the conclusion. But I think the larger part of whether the conclusion is true is whether the premises themselves are true. The premises usually aren't just facts, but an outlook, a framing, a kind of model of the world, which setup the kinds of ways we reason from the facts to the conclusions.

Understanding why a map is a map of a particular territory can help us to avoid confusing that map for the territory

Jurors are biased by animated recreations used in courtrooms.

Things we don't understand always seem intangible.

The tendency to assume that things are as we perceive them. An example of this is assuming that since qualia seems inexplicable it is so.

We often wrongly attribute properties to objects that are actually the properties of interactions. For example, that something is addictive has to do with how our bodies/brains process it, not some intrinsic 'addictiveness' property of that thing. So non-physical things (like activities such as video games) can be just as much addictive.

A link to a 10 minute video on what it means to be open-minded (direct link).

On intuition. Distinguishing between learned-intuition and heuristic-intuition. Reason and intuition both have their place, but reason is better for determining which of these is better to use in a particular situation.

False neutrals. Assuming that only alternatives to the status quo, which itself is considered 'neutral', need to be subjected to evaluation.  And trying to understand why we fall prey to false neutrals.

Janet Rae-Dupree argues that innovation is the result of hard-work, not flashes of brilliance (direct link). An article on the myth of prodigy: "A study of 200 highly accomplished adults found that just 34 percent had been considered in any way precocious as children" (direct link).

An important part of how we 'naturally' view things in the world involves, I think, essence-based things and a predominantly social/aesthetic interpretation.

A blog post (direct link) by John Hagal on an article (direct link) by Rich Karlgaard on the prevalence of, and problems with, zero-sum thinking.

In cool reflection, it's easy to underestimate the force of emotions. When you experience emotions it affects you. But when you imagine such a situation they don't (or to a much lesser degree). This makes it easy to underestimate the force of emotions, and overestimate the ease of just doing what you want.

Motivation is often overlooked as a kind of emotion, feeling or desire. I have a brief look at what factors can influence motivation and why it's not a simple matter of "wanting to do" the thing.

David Deutsch's reply to the 2001 Edge question, arguing for the importance of looking for explanations for what we see happening (direct link).
"What is it in reality that brings about the outcome that we predict?" Whenever we fail to take that question seriously enough, we are blinded to gaps in our favoured explanation.
I think F. Scott Fitzgerald's test for intelligence embodies a good notion of what intelligence is
The test of a first-rate intelligence is the ability to hold two opposing ideas in mind at the same time and still retain the ability to function.
Some posts related to that. I think it's an important skill to be able to reason about an issue without the implicit assumption that your position on it is true, and I talk a bit about what is required for doing this. It's good to understand views that you reject. Why does it make sense to others? Doing this can help guard against rejecting things simply because they seem "ridiculous" to you.

On the common but mistaken view that 'how much general knowledge you have' equates to how smart you are.

We think of size in relative-terms, relative to our own size. But this is very misleading. It's more accurate to think of something's size in terms of the amount of 'atomic' detail it consists of, and in such terms everyday objects like ourselves are very large.

Despite how perception presents the world to us, the actual physics (of "subatomic particles", so to speak) is everywhere and everything.

When we think of a book we may think of the physical object, with pages and ink printed on them. But we may get a, in some ways more accurate, picture of it by imagining it as the sequence of letters, spaces and punctuation that make up the book's content, as if that was arranged in one long line that stretches out for quite some distance.

Just an interesting thing to think of: as well as the physical Earth, there is each person's personal conception of the world, the one they actually see and experience in their heads, and there are billions of these.

Physicist Brian Greene: "The difference between making a breakthrough and not can often be just a small element of perception".

Non-experts can be better at solving problems than the experts - an example.

On the tendency to dismiss things

Some miscellaneous examples of this. There seem to be endless cases of these. What follows is a just a small grab-bag of cases I noted down.

Medical. Where a mother died after her emergency call was treated as a prank. Where a woman died because she was ignored in the emergency room of a hospital. A woman had 17cm scissors left in her after an operation, and she had a huge amount of trouble getting people to believe she was in real pain and that there was something wrong. The person who discovered that duodenal ulcers were caused by a bacteria not stress was ridiculed for holding this view.

The natural world. Giant ocean waves were long dismissed as myths, despite the fact that they actually exist (as has now been definitively shown).  Early reports of geysers weren't taken seriously.

Systemic Worldview

The world works in systemic ways, so the ability to think in systemic terms is so important.

People tend to think that the only or best way to address problems or to achieve goals are with 'vertical' (domain or problem-specific) solutions.  But I argue that 'horizontal' (domain-agnostic, often 'infrastructure') solutions are often more important (the linked post is talking about this specifically in the context of software).  Vertical solutions are appealing because it seems they're directly focusing on the goal you want solved, while the latter seems spread too thinly.  The key to appreciating horizontal solutions is that instead of being for a specific goal they help enable them.  (This is closely related to the distinction between applied and fundamental research).

It's important to appreciate the kinds of 'systemic effects' that can make systems work in counterintuitive ways.  Such as when incentives are poorly aligned.  Some examples of this, to do with why enterprise software is so often poor.  Another example - Bruce Schneier's notion of CYA (Cover Your Ass) security: "much of our country's counterterrorism security spending is not designed to protect us from the terrorists, but instead to protect our public officials from criticism when another attack occurs".

An example of systemic effects.  In the article "Internet Killed the Alien Star", Douglas Kern contends that the UFO movement has been largely killed off because of the internet and other technological developments, such as camera phones.

Change is messy, and this is under-appreciated in practice.  In 2009 Clay Shirky wrote "Newspapers and Thinking the Unthinkable".  Newspapers are going away, it'll take some time to invent alternative venues for journalism, and the whole process will be messy (and how the history of printing press can help us understand this).

Chris Anderson article 'The Probabilistic Age': "Our brains aren't wired to think in terms of statistics and probability." (direct link)

The following subsections are cases of concepts that help in appreciating things in systemic terms.

A broader notion of affordances

Donald Norman's notion of affordances: the character of physical objects suggests how we can interact with them.  I think there's value in a broader notion of affordances: the character of entities (whether physical objects, or things like mental concepts) shape how we perceive, think about, or do things.

It's very easy to underestimate the affect of convenience and reminders in determining whether a person will actually undertake some activity, so we tend to underestimate the importance of affordances.

An example of software affordances: when there's a language for creating some data (e.g. a templating language for generating HTML pages), the degree to which the form of the code matches the form of the data to be generated is an affordance.

Some more examples of affordances, and the utility of having a very general notion of affordances.

Evolution

Our usual language for talking about evolution tends to be misleading, so I suggest some alternatives. And, prompted by a comment on that post, some elaboration.

Most people only understand the definition of evolution, which by itself provides a misleading picture of it.  To be able to think sensibly about evolution requires understanding a bit about what evolutionary processes are like in practice.

Some miscellaneous things relating to evolution:

The Copenhagen Interpretation of quantum physics and the theory of evolution seem fundamentally at odds with each other, and the latter has much better evidence in favour of it.

Could debilitating grief be, in part, a 'precautionary tale' to help others avoid whatever caused it?  This could have evolved through kin selection.

Could our 'inner voice' have evolved as a way to re-use existing machinery (for processing external voices) for a general-purpose intra-brain communication mechanism?

The Intelligent Design movement claims that natural selection couldn't have produced lifeforms.  Lifeforms are too complex, they say.  But even if that were true, why don't they consider the possibility that life's the result of some other, as yet unknown, naturalistic mechanism?

Most descriptions of microbial evolution avoid using the term 'evolution', and this "may have a direct impact on the public perception of the importance of evolutionary biology in our everyday lives.", says a (quite readable) article in PLoS Biology.  Related to this, doctors who don't appreciate that antibiotic resistance is an evolved trait tend to prescribe antibiotics in a way that encourages such evolved resistance -- leading to so-called superbugs.  I link to a blog post on this topic.

Reductionism

'Reductionism' is very often misunderstood.  I try to clarify what it really means.

A simple case where reductionism appears wrong but isn't: stacking two planks of wood does more than increase the overall strength by two.  The flaw in the reasoning stems from treating an abstraction ('strength') as a literal thing.

The whole is greater than the imagined coming together of the parts: usually when it's claimed that "the whole is greater than the sum of the parts" in some situation, that claim isn't based on a precise, concrete understanding of what the "sum of the parts" really is, but more just on an intuitive impression of what the "sum of the parts" would be.  This is another flawed reason why people thing reductionism is wrong.

Laddered skills

Skills are 'laddered': you have to go through the lower-rungs on the ladder to get to the higher-level or more advanced competencies.   Lower rungs tend to be simplified, rough capabilities; higher-rungs tend to refine them.  It's often assumed that the results of advanced competencies can be achieved by simply knowing what they are and trying hard enough, but it takes substantial time and practice to work your way through the rungs up to that level.

It's difficult to imagine higher-rungs above our skill level, which intuitively makes it feel like they don't exist.  It's difficult to imagine how we'd reach a higher-level, which makes it feel like there isn't a point in trying.  And it's difficult to imagine what having a high-run ability would enable, which makes it feel like there wouldn't be a point anyway.  But these are just limitations in our abilities to imagine, which we should expect to experience and which we should ignore.

Acquiring knowledge is acquiring a skill.  As we learn a skill we refine our abilities, and develop fluency.  I suggest that acquiring knowledge is literally a matter of acquiring skills, and follows this same pattern.

Being able to explicitly reason about a concept is a skill.  One rung on the ladder of cognitive skills is being able to explicit reason about concepts.  Doing so requires being able to override intuitions and a fair bit of practice.  It's an important skill for being able to draw reasonable conclusions about a topic, which also means that non-fiction books arguing for a particular conclusion should pay heed to this and try to help the reader develop skills in reasoning about the concepts involved.

Laddered skills don't just apply to individuals, they also apply to organisations, like companies or countries.  A society has to have developed to a certain stage before it can maintain a democracy, for example.  Democracy can't be installed into a primitive society in one fell swoop or just by "trying hard enough" to install it.  I'm curious about how societies evolve.  What are the rungs, such as in how how legal systems and other institutions come to be and get fleshed out?



Computing

How I think file-system tagging should work.  To be truly viable, the tagging system needs to utilise hierarchy in two ways: hierarchical tag namespaces, and tags being scoped to sub-hierarchies of the directory hierarchy.

Minor:

Simulations, for teaching learner drivers, could present them with the sorts of unusual circumstances that can cause accidents (e.g. another car suddenly behaving erratically)


An idea - a smart-phone 'slush pool' for making small payments practical: the user gets convenience because they can make small purchases using this 'slush pool' without needing to enter a password, and at the same time have minimal risk because they require a password to add money to the slush pool and it can only ever contain a small amount of funds (e.g. a max limit of $10).  [Written in 2010 - recent technologies like fingerprint and facial identification lessens the need for such measures].

Is there a way to incentivise and support summaries of threads on discussion sites like Reddit?


Would it be useful to have a "Stack Overflow" for finding research material in a subject area?  It could help people from outside a field (including those trying to get into the field) to find out about relevant research in the field, from people in that field.  I discuss the issue of incentives for contributing to such a resource.  Perhaps this need has been, since writing this post, served by Quora or some subreddits.  I'm not sure.


Immersive language teaching.  2004 article on software developed by the University of Southern California to provide an immersive virtual environment for learning language in a more natural way.

Using Wikipedia as a source of canonical tag names.  To get the canonical tag name for a subject, get the URL of the wikipedia page for that topic and use the right-most part of it as the tag name. e.g. Ten-pin_bowling from http://en.wikipedia.org/wiki/Ten-pin_bowling


User-interface

Minor:

A user interface principle: operations should be applicable to a type of information, regardless of the context it appears in.  If an operation can be applied to an X, it should (unless there's a good reason not to) be able to be applied to Xs anywhere they appear.

Visually referencing web-page elements: we could provide better support for users to provide visual references to elements of webpages or applications, to help in writing instructions for using them.  To enable showing rather than telling.

Some minor ideas for operating-system user interfaces.  For switching between windows: hit a shortcut key then gesture mouse in direction of desired window, or have the shortcut key bring up a small schematic map of desktop at mouse-pointer location.  For file-explorers, have an optional 'Recent Folders' navigation pane.  In the top-half of the left-hand pane, it lists the folders you've recently navigated or moved/copied files to.

Dealing with files in a higher-level fashion: not needing to specify a name or location for the file, and not needing to explicitly save them.  The posts go into some specifics of this: Sep 2007Jun 2008Mar 2009.  This is an area where the software landscape has changed since writing these posts, with the way things like Google Docs and mobile apps operate.

Different communication mediums have different affordances.  One dimension these affordances range along is from encouraging more lightweight and transient content (twitter, chat), to encouraging content that's more substantial and longer-term (e.g. email).  Would it be useful for this to be explicitly acknowledged by the software tools, such that a conversation could be 'promoted' from a lighter-weight medium to a more heavier-weight one, when that made sense, where by this transition was seamlessly handled and tracked by the software?

A couple of thoughts on what the smart-phone analogue of Vim-like modal editing would be.

Fan menus: an idea for taking the combining the best parts of radial/pie-menus and conventional context-menus. The menu rendered like a conventional context-menu, with an additional radial element for more quickly selecting between the menu items. (After having prototyped this, I don't think it quite works, but I do have an idea for another variation that might work better.  I intend to write it up sometime).

Some minor ideas for visually representing information in software tools.  For word processors or text editors.  When searching for text, display something like a mini-map to show an overview of the occurrences in the entire document.  (I wouldn't be surprised if this has been implemented in some tools by now).  A facility for showing recent changes to the document (in a fashion like Word's 'Track Changes'), indicating the order the changes we made in, and giving control to the user over the time period to show changes for (e.g. 'today', or 'last 3 hours').  Being able to automatically make more concise representations of information, and to dynamically adjust the level of detail in the representation.  Making it concise by tailoring it for a particular person and/or purpose.

A few basic ideas for weather forecast sites/apps.

Copy-editing marks and annotations.  The Signal vs Noise blog argues that copy-editing marks are better than how 'track changes' edits are rendered, and I see this as an example of our current software's generally poor handling of annotation.

A couple of user-interface ideas.  'Highlighting equivalent links' in the browser: if the user mouses-over a link, and the page contains any other links pointing to the same destination, highlight those as well.  Hold-and-swipe touch-screen gesture - an advanced gesture that could be utilised on touch-screen devices: the user holds their thumb on the screen while swiping with another finger.

Idea: personal subject-lines for emails.  Instead of seeing software as presenting an objective view of information, see it as a personal tool for the user, suited to how they see things and how they want to use it for the tasks they're trying to achieve.  For example, instead of an email inbox simply showing the subject-lines of the received emails, why can't the user change what it says for a subject-line, if that made it more informative for them in the context of how they're going to use that email, or where it'd make it easier for them to find it in the future?

Magic Ink: Information Software and the Graphical Interface, by Bret Victor is a powerful argument for why, in designing software, greater emphasis should be given to graphic design and less to interaction.  All his writings are quite good, and worth a read.

Visualisations

These aren't necessarily computing-related, but it made sense to me to put these next to the user-interface section.

Minor:

Cecilia Burman provides an effective way of showing what prosopagnosia (face blindness) is like
"If individuals were rocks, then it's like having to remember the characteristics of each rock, and try to realise when you come across this rock again, from your memories. The page uses photos of different rocks so you can see for yourself the sorts of difficulties involved."
A map someone has done of US states, where states have been renamed for countries with similar GDPs.

An antipodes map someone has made: select a location and see where the exact opposite side of the world is located.


Jon Udell's idea for augmented reality map views (e.g. that could label the details you're seeing outside an airplane window).

Having historical overlays for Google Maps: A service like Google Maps could have a date-slider that allows you view the world at different times in the past, and see the different country names and boundaries and the like.  It could even show particular culture's views of the world at a particular time (what places they knew of, and what they called them).

Australia is a large land-mass, but the actual size of the populated area of Australia is much smaller.  It would be interesting to be able to visualise this, and compare it to the size of other countries.  (And of course, it would be interesting to see such details for other countries, too).

Lokesh Dhakar's visual catalogue of types of baseball pitches.  Each picture is a simple graphic that intuitively captures the essential character of a type of pitch.

Video of Hans Rosling showing some impressive visualisation of statistics using the Trandalyzer tool.  Graphs are used to show the statistics, but interactivity and animation is used to show changes over time, to transition between related perspectives, and to drill down into more detail.  There's an impressive flow: one perspective raises certain questions, so he modifies the view to try and get insight into them.

Imagine being able to visualise the exact location of a piece of meat (e.g. a steak) within a 3D rendering of the animal it came from.  Or within an animated rendering of the animal, as it's grazing around in a paddock.  As a way of making visible a reality we know is true but can't see.

Taking before-and-after shots of things like house construction from the exact same positions and angles, would enable better comparison.

Links to some visual illusions.  A face that looks calm when viewed up close, but angry when seen from a distance.  Invisible changes: images that are continuously changing but which appear static.  A large collection of various optical illusions.

Extending cut-and-paste

I think it'd be beneficial for software to better support working with structured information, and to allow users to do so in a fluid way.  The following is one possible area for doing this.

Introduction.  The motivation for these features is to provide a more direct way for users to convert their intentions into actions. (In passing I'll note that this is also the main benefit of the Vim text editor).

Being able to view and interact with the clipboard contents in a window, and being able to edit these contents (and the motivation for this).

Allowing multiple clipboard items, and some reasons for wanting this: (1) repeated pastes of an item, interleaved with unrelated cut and paste operations, (2) interactively searching for the same set of terms in different documents, (3) batch copying, and (4) a specific case of batch-copying from an online bibliography.

Storing clipboard history.  Being able to select multiple items in clipboard contents and history.  Being able to 'peek' at the next paste item.

How more complicated cut-and-paste operations could be specified, by using CTRL+SHIFT to add modifier keys.  How such operations could be specified for text copied from context-menus such as "copy link location" in a web-browser.

Controlling where in the clipboard list to cut/paste to/from, and whether a cut/copy replaces an existing item or inserts a new item, and whether a paste leaves the item in the clipboard or not.  Cut/copy the item at the end, or at a specific position (either replacing the item already there, or inserted as a new item there). Paste from anywhere in the list, and 'pop-pastes' that remove the pasted item from the list.

Multiple items in the text may be separated by delimiters (e.g. commas).  Cut/copy these as individual items in the clipboard list ('split copy', and some concepts for thinking about this, as well as some motivation for it).  And pasting multiple items from the clipboard as text separated by specified delimiters ('joining paste').

Template paste: paste a 'template' containing the contents of multiple clipboard items.

Formatted paste: when pasting from rich-text documents into plain-text ones, be able to automatically convert rich-text formatting (bold, italics, etc) into plain-text equivalents (e.g. *bold*, /italics/).

Thinking about software

"Non-functional" aspects of software (like usability) are very important, yet new software is often dismissed because it doesn't do anything that existing software can't.  IT people, in particular, have a very strong tendency to compare software only in terms of the functions they can perform.  An example of this: the claim that choice of implementation language doesn't matter.  Affordances are an important kind of non-functional property of software.

Software is a tool, and we can't predict exactly how users will use tools (a quote relating to this, and an example).  We should acknowledge this in the design of software.  I believe that, ideally, a piece of software would be a program written in it's own very high-level domain language.  For example, the WinAmp program you get would be a program in the WinAmp domain language.  The grammar of this language would define all the ways we can compose the components of that domain language into valid WinAmp programs.  That is, we can customise the program by changing its high-level source code.

Some Alan Kay quotes on computing as the first 'metamedium' that can 'dynamically simulate the details of any other medium'.

Programming

Minor:

Even if you're a solo developer, programming is always a team activity.  The other members of the programming team the future versions of yourself 6, 12, 24.. months from now.  A reason why you should always write code for others to read.

Defining functions within functions: if function A is only going to be used within function B, the code could be made clearer if a language allowed function A could be defined within B (at the start of it).

Sequences of lines of code may form a logical unit, but be too lightweight to break out into a separate function.  We may want to document the overall function of such sequences, or even just indicate that they form a logical unit.  Comments may be used, but there's no good way to specify the span of lines a comment applies to, so it could be useful to have a lightweight way of indicating that a sequence of lines forms a logical unit, and the post discusses how this could be done and how it'd enable those units to be 'collapsed' to provide a more concise view of a function.

When an experienced programmer is trying to learn a new language, what's the most efficient way to present them with what they need to know?  I suspect it's to provide concrete examples of the features, which show the syntax and the results you get for particular inputs.  Essentially, a collection of simple, representative examples, showing the exact inputs and outputs.

Teaching Programming

An idea: using a game to teach regular expressions.  For example, use regular expressions to attack oncoming patterns of enemies.

Against 'simple' as meaning 'fewer elements'

Software being simple doesn't equate to having fewer features, and software being complex doesn't equate to having more features.  Simplicity means being well-tailored to user's needs.

To explain this viewpoint, outlining the notion of 'qualitative perceptual concepts', and arguing that complexity is one of these concepts.

Local vs global simplicity.  What can make some software seem simpler, from the perspective of that software by itself (at a 'local' level), can actually make it more complex to use in practice, in the context of the user's use of it and other software it's used in conjunction with (at a 'global' level).

Initial vs standing simplicity.  How simple the software is initially, vs how simple it is for an experienced user.

Looking at the value of potential new features in isolation, rather than its potential benefit as part of the entire system, is a reason that software can become too complex.

Others have argued against 'minimal features' view of simplicity, and for simplicity as primarily meaning the software suits the user's perspective and tasks: Joel Spolsky (who also brings in the notion of 'elegance' meaning 'grace and economy at achieving some task'), and Dharmesh Shah (1) and (2, which also argues that software should be 'opinionated' but not 'stubborn').

Avdi Grimm teases out the various different sorts of simplicity, and the tradeoffs involved in each type.

More choices may mean more complexity, but there is some nuance to this.  How many choices you need to deal with at once is the bigger issue.

(I think this post I wrote is a bit muddled).

Education

Minor:

A goal for education: giving people confidence in their learning ability.

On Producing High-Quality Work

Minor:

Mostly this is about having high standards.

Links to some articles/posts on this.

"It's easy to make something incredible" - link to a blog post on how high-standards are basically all that's required for producing great things.

Steve Martin: "Be so good they can’t ignore you" (i.e. have really high standards)

A bit more indirectly on this point:

An AV Club interview with Ricky Gervais, including his thoughts on creative control
AVC: How do you establish that kind of creative control?
RG: I just demand it. I just simply wouldn't do anything that I wasn't terribly in charge of. I don't let anything go.
'Personas' provide requirements that are too vague (comment on a 37signals post). An example that I see in terms of high standards being central to producing high-quality creative work.

An article on the design process used by Apple's chief designer, Johnathan Ive.  Using intense iteration and trying really hard to find any flaws and areas of improvement.

People often argue against having high-standards on the grounds that it's perfectionism, and perfectionists get stuck and can't produce output.  This is a failure to distinguish between the 'immobilised perfectionist' and the 'persistent perfectionist'.

Philosophy

Just because something has always been a philosophical question doesn't mean it will always remain so.  We may obtain a concrete understanding of the matter, whereby it will become science.

There's learned philosophers but not philosophical experts.  Philosophy concerns what we don't have a clear understanding of.  It involves discussions and arguments and all the back and forth between these.  Progress is in clearing up confusions, and making finer points.  This means there's no established knowledge to have expertise in.  Instead, being an 'expert' means being more learned in the ins and outs of the web of philosophical discourse.  This has significance for the potential for outsiders, not part of the philosophy discipline, to make contributions to philosophical topics.

On writing, presenting, researching, getting things done

Minor:

Paul Graham's essay "Persuade xor Discover": writing to persuade and writing to discover are diametrically opposed, which is important to realise if you wish to discover (direct link).  

Some Signal vs Noise posts on communication: on usefulness of counterintuitive-seeming statements, for getting people's attention; on how "the Curse of Knowledge" makes communication difficult; on describing a slice instead of the whole pie'; and on what being a speechwriter is like, and how it's similar to doing graphic design.

A list of authors I think are good at non-fiction communication (written in 2005).

Edward Tufte's presentation tips (direct link).  Some presentation-skills lessons from Job's iPhone talk: build tension, stick to one theme per slice, add pizzazz to your delivery, practice, be honest and show enthusiasm (direct link).

Richard Hamming's advice on doing research - "You and Your Research" (direct link).  I tend to find most advice on doing research a bit ordinary, but I thought this was quite good.

Paul Graham's essay "How to disagree" (direct link).  See this also.

Rough notes on getting things done.

A Signal vs Noise post 'Do it yourself first', on why it's really beneficial for you to have tried to do a kind of work in a company before hiring someone to do it (direct link).

Misc ideas

'use by' labelling on food could be improved by distinguishing between 'use by, if unopened' and 'use by, once opened'.

An idea for between-floor transportation in buildings, combining hop-on-anytime convenience with a small horizontal footprint.  In spaces that are too small for escalators, you can have lifts, but they don't have the same hop-on/hop-off convenience. Something that's both compact and has that convenience could make the second or third floors in such spaces more practical for commerce.  Could it have other effects, such as helping people in companies spanning multiple floors communicate and collaborate more effectively?

Two thoughts about taxes.  1) Taxes would be better framed as a contribution to society rather than a deduction.  2) Journalism should be funded by taxes, because it's exactly the kind of public good that taxes are intended for -- an important infrastructure that market forces aren't suited to funding (it has strong biases against good quality content).

Imagine a large coffee-table book, with one page for each country in the world.  For each country's page, imagine a single large photograph.  Think of something like a high-school class photo, but with a larger number of people in it -- something like 200 (instead of four or five rows of people, maybe there seven or eight).  Where those 200 people have been chosen to represent the ethnic diversity of the people in the country, and something of the variation within each of the main groups (perhaps 200 people wouldn't be sufficient, maybe 300 or some other number would work better; and yes, whatever set of individuals was chosen would involve some degree of controversy, but there is positive intent behind this idea and some degree controversy shouldn't be a roadblock).  Obviously, any such thing would be a major approximation of the actual range of people in the country, but the idea is that even a book containing such major approximations would give most people a greater sense of the diversity out there than they currently have.  Personally, I think such a thing could be quite interesting.  It's obviously something that could be done as a web-site, too.

Allowing wiki-style edits on every single web-page.  A potentially practical way for this to work, and why it could be useful.

An idea for a multi-touch rhythm game, where player needs to perform actions like tapping at three positions on the screen at once, or tapping at two locations, then sliding their those two fingers along a path.

Smartphone user-interface idea, "Flow forms".  For quickly entering in data that's a sequence of multiple-choice options.  The sets of multiple choice options are laid out one after the other, and there is a vertical 'channel' for each choice option.  The options automatically scrolls up the screen, and user moves finger left or right to select which option as it passes.  So the user doesn't have to lift their finger, just move it left and right.

Reframing how digital content is sold, from you paying for the content itself to paying for the effort that went into creating it.

Metaphor appears to be deeply embedded in the character of our language and thought (c.f. Lakoff and Jonson).  Should we thus focus more on such metaphors when teaching languages?

Minor:

As an alternative scheme for presenting footnotes, write the main body of the text as if it had no footnotes and at the end of each chapter have a 'footnotes' section where, for each footnote, there's a recap of the details from the main body of the text that it is for.

It'd be interesting to have a documentary that covers the differences between fictionalised accounts of police or medical work and the actual character of the work in those fields.

Smartphone app idea, "Battlechat": a competitive real-time text chat game.

Remote-controlled cars or drones could be used as like a Logo-turtle, for teaching programming concepts.  There could be more of an emphasis on navigating the physical environment.

A laptop with a screen you could raise-up might have better ergonomics.  (I know at least prototypes of such designs have been made).

Misc points

History is all that's happened: history isn't just significant events and 'grand narratives', nor does it just include things that happened a fair while ago -- it's literally everything that has happened.  This is important, because the important things we can learn from history often involve conclusions and patterns drawn from less 'historic' seeming details. 

Structure makes structure: once there's some structure in a system, that will tend to lead to more structure, leading to more structure, and so on.

Does the existence of spam emails help to make us more critical consumers of information?

We see resolve as an expression of free-will, but resolve can be seen in a way that doesn't involve free-will: as cases where, in our conflicting desires, the 'good' ones outweigh the 'bad' ones.

A quote on the importance of paying attention to initial impressions, to help preserve an accurate account of things.

Assuming that 'every little bit counts' is counter-productive.  Resources are limited, so priorities are very important.

Exploitation of poor workers is more about poor treatment than low wages.  Low wages are not the the evil they're usually made out to be.  They're genuinely important.

Chemicals can be completely natural.  On the mistaken notion of 'chemicals' amongst the general public.

Don't be afraid to express non-unique points of view.  We may look down a little on saying things that have been said before, with it being seen as better to develop new understandings and viewpoints.  But doing so can help organise your thoughts.

Strong leadership of the JFK "moonshot" sort might be what's needed to tackle climate change.  One incentive for this is it's an opportunity to be seen as a hero to people in other countries and to future generations.

An analogy to show that, even though qualia seems so inherently mysterious, it need not actually be so: imagine a person in a remote tribe who knows nothing about modern technology, who is given a handheld games console.  Nothing from their knowledge or experience could suggest what the game world is or how it might work.

A short quip: "Unseen practice is easily mistaken for brilliance".

Misc

Minor:

Nassim Taleb on the lack of respect for those not doing steady and predictable work.  Matt Inglot on society's attitude towards people who don't have a "real job": "the fear of ... doing something different, something with an unsure ending" (direct link).

Michael Bloomberg's speech, defending scientific values.  In his address to graduates of Johns Hopkins University School of Medicine.

Jaron Lanier writes about the anti-intellectualism in today's society, the need to overcome it, and suggestions on doing so. One of the topics he focuses on is spirituality and how that can mesh with a naturalistic worldview.

Daniel Dennett's policy recommendation that every child is taught about all world religions (direct link)
Toxic religions depend on enforced ignorance of the young -- and a religion that can flourish in an informed (citizenry) is a benign religion.
A post on Kuro5hin arguing that advertising should be taxed, because of its negative effects (direct link).

I agree with the sentiment in Chris Mooney's article "The Monster That Wouldn't Die" (direct link)
I'm tired of preachy retreads of the Frankenstein myth, first laid out in Mary Shelley's 19th-century classic and recycled by Hollywood constantly in films from Godsend to Jurassic Park. I'm sick of gross caricatures of mad-scientist megalomaniacs out to accrue for themselves powers reserved only for God. I'm fed up with the insinuation (for it's never an argument, always an insinuation) that there's a taboo against the pursuit of certain kinds of knowledge and that certain technological achievements -- especially those with the potential to affect life itself -- are inherently "unnatural." 
... 
I'm extremely uncomfortable with the way in which the weapon of the Frankenstein myth is repeatedly used as a club against modern-day medical researchers, who are seeking to cure people, not to become God.

Kevin Kelly looks at how, when copies are free, you have to sell what can't be copied (direct link).  He goes into the sorts of non-copyable things that can be sold.  I outline some thought about this in terms of the view of technological development as the removal of constraints, and on why that view of technological development is useful.

Related to my PhD

My PhD Scholarship Application.

On distinctions made between 'data', 'information' and 'knowledge'.  What we really need is a better understanding of the phenomena.  It isn't very helpful to try to make sharp distinctions when our understanding is lacking.

A grab bag of things with some relation to my PhD work:

Paul Graham on discarding the assumption that it's all about us (direct link).  I believe this is key to understanding the foundations of information and semantics.
if you want to discover things that have been overlooked till now, one really good place to look is in our blind spot: in our natural, naive belief that it's all about us.
The computer revolution as a switch to imperative descriptions.  In "The Structure and Interpretation of Computer Programs", Abelson and Sussman write:
The computer revolution is a revolution in the way we think and in the way we express what we think. The essence of this change is the emergence of what might best be called procedural epistemology--the study of the structure of knowledge from an imperative point of view, as opposed to the more declarative point of view taken by classical mathematical subjects.
(Wolfram argues similar points)

How explicit does a representation have to be?  Is there really a hard distinction between explicitly and implicitly representing some details?  I suspect not.

Sunday, July 08, 2018

How I think file-system tagging should work

The idea of file-system tags makes intuitive sense.  You might have files of different types -- documents, text files and images -- stored in dispersed places in the directory hierarchy, that may all share a common characteristic, such as all being recipes. The directories containing those files might also contain a whole lot of non-recipe-related files (e.g. one of those directories might be for your website and contain a lot of files that aren't recipes).  If you can tag all the recipe files with a 'recipe' tag then you can get a listing of all those files, and only those files. Or, as another example, you can restrict a search to be only within that collection of files.

Directory structure provides the primary basis for organising, and thus finding and viewing, collections of files. Tagging provides another layer on top of this, where files that may be unrelated in terms of directory structure can be related by the tags they share.

Nowadays, mainstream operating systems like Windows and macOS include some sort of file-system tagging.  (I should note that I only have direct experience with tagging on macOS, and have only read about how it works on Windows, so hopefully there won't be any inaccuracies in my depiction of that).  While I think tagging is a good idea in principle, I think that current importations of the idea leave room for improvement.

There are two common properties of tagging systems that I think can be improved:

1. the tag namespace is flat
2. tags are global

I think it would work better if:

1. tag namespaces were hierarchical
2. tags were private to particular directory subtrees

Why?

In short, hierarchy is an important tool for organising information, and that's what these two suggestions are about.

When the tag namespace is flat, there's a single tag namespace and all the tags are at the same level within that.  This gets too unwieldy. You might have a set of tags associated with recipes, like for the dish type (entree, main, dessert), and for cuisine type (italian, chinese, mexican, etc). But then if you have other sets of tags for other topics unrelated to recipes, the overall collection of tags can soon get too unwieldy. When trying to find a recipe-related tag from the list of tags, you have to find them from amongst all the other tags.

Being able to partition the tag namespace in a hierarchical fashion would help this.

At this point we can note a trade-off at work here.  In some sense, the whole point of tagging is to escape from hierarchy, to be able to specify categories that cut across the hierarchical structure of the file-system.  A tag like italian could be applied to recipes, but also songs and images of paintings. Applying a hierarchical organisation to tags goes against this. But, it doesn't go totally against it. Even with hierarchical organisation of tags, any tag could still be applied to a file anywhere in the file-system. I believe that a flat global namespace for tags is too unwieldy, so I think the tradeoff is a reasonable one.

One way to do this would be for there to be a global tag namespace, which is then hierarchically structured.  On the top level there might be tags like recipe and work. Under recipe we could have the tags like those listed above: entree, main, desert, italian, chinese, mexican, etc. Under work there'd be various work-related tags, and so on.

Like how I've argued that a flat namespace is too unwieldy, so I think a global namespace is too unwieldy.  My solution for the flat namespace was to make it hierarchical, and similarly my solution for the global namespace is to have a kind of hierarchical partitioning of it.

I think it would be better to associate tag hierarchies with particular directories (or more specifically, the directory subtree rooted at that directory), where the namespace for the tag is only within that directory subtree.  Where, outside of that subtree, those tags do not exist.

Despite tags allowing us to cut across hierarchical structure, we may want to only apply tags to files within a particular directory subtree.  Perhaps some tags are only for music files, which are only under the ~/music directory, or photos, which are only under the ~/photos directory. Or if we need the tags to be a bit more general we could put them in ~, or if we do want some to be even more general we could put them in / or C:\.

In terms of GUI file managers like Finder, their side bar could show only those tags that are applicable within the current directory.

Such a scheme would limit the ability of tags to cut across hierarchy, but I think it is a reasonable tradeoff.

Tags are ultimately a kind of metadata about the information in the directory structure, so it makes some sense to organise the tags within the directory structure, associating them to some extent with the information they're about.  A global namespace does not allow specifying any details of how the tags relate relate to the organisation of the information they're about.

Associating tag hierarchies with directory subtrees would make it more explicit as to what the intended use of the tags is - that is, what sort of information they were intended to classify. That, for example, dog is meant to be for pictures of dogs, not for any file in some way related to dogs. If we start using tags in a more haphazard fashion the entropy in the tag use increases over time.

One way to think of this is that, what we're looking to organise is not just, one the one hand, the directories and files, and on the other, the tags, as if these were separate concerns.  We're looking to organise the overall structure including both the directories-and-files and the tags, and how they relate.

Friday, February 02, 2018

Using interaction in a narrative media to enhance the focus on character perspective - sketching a high-level vision

I'm interested in a kind of narrative media where a primary focus (in the whole, or elements of it) is placing the 'player' within a character's shoes (immersion to foster empathy with the character), and where serving this goal is the primary focus of the interaction.  Computer games already use interaction to place the player within a character's shoes, but I think there's some directions they haven't yet explored.

What I'm interested in exploring (at some time, post-PhD) is a bit like a computer game, but not necessarily a game, and a kind of interactive storytelling, but not necessarily focused on a story.  I'll try to give a high-level view of these thoughts here.

A word of warning: this is all based on intuitions that I can't, at this moment, fully articulate or back up.  Seeing if anything could be made of these ideas could only be done by experimenting and actually trying them out.  In this post I'm trying to flesh out a kind of launching-off point for such experimentation.

Imagine a life pretty removed from our everyday modern lives.  Like a lowly worker on a sailing ship in the 17th century spice trade.  What was their day to day life like?  What sorts of activities did they undertake, and what was the character of those activities?  How did they see the world, and interact with the other people (of various stations and standings) on the ship?  What did they want out of life?  Imagine if you could see their day to day life through their eyes, and hear their thoughts, and use interaction to have a role in carrying out the activities they go through.  This the kind of thing I'm thinking of.

You could try doing this kind of thing as the main focus of the entire work, or it could be done here and there within a more conventionally narrative-focused work.  Again, experimentation would be required to see if either of those would work.

I suspect that the basic way of achieving the goal would be through something akin to quick-time events (QTEs), and the overall work being made up of QTE sequences.  The primary purpose of the QTEs would not be, as is sometimes the case, providing a challenge for the player, but placing the 'player' in the character's shoes.  To try to get them to perceive and think about the details presented to them in a different fashion to how they would the details in a novel or a movie, more like as if they were in that situation and getting more into the character's mindset.

Here's some thoughts about how this could be done.

(And yes, QTEs can suck, but I think there's scope for exploring different ways they can be implemented.  The devil is always in the details, and subtle differences can make all the difference in practice).

QTEs could be used in a more granular way, which would mean more frequent interactions.  The rationale for this is that the activities the character undertakes have a structure (there's a number of moment-to-moment steps the character undertakes to help set up a sail, for example), and if we want to place the 'player' in the character's shoes, then we want them to click/tap/swipe to "step through" each element of what the character is doing.

To help place them in the character's shoes, the 'player's perspective could be either a first-person one, or a third-person one such as an behind-the-shoulder one that provides a view of what the character is doing but which is still relatively-close to a first-person view.  So the QTE interactions would be presented from such a perspective.

As well as using the interactions to initiate elements of an activity, they could be used to shift where the character is looking or what they are focusing on.  So if they are reefing in some ropes but then need to look up to the sail to see how much of it has been pulled up, the 'player' could click to shift the character's perspective upwards.

There could be text labels on the QTE targets, indicating what the action is that the player will be initiating, to help them understand what the character is doing (or rather, about to do).

As well as, or instead of, such labels, there could be narration from the character, about what they are doing and/or thinking.  (There might also be a way to engage the 'player' by having them predict or anticipate what the character is going to do, and in some small way reward them for correctly doing so.)

A typical narrative tends to show only plot-relevant details.  What I'm thinking of could include more of the details that show what it's like to be in the character's shoes, such as showing the detailed steps of what they are doing in setting up the sails.  Such details would likely be tedious in a non-interactive format -- just detail after detail after detail*.  The hope is that such details can be interesting, rather than boring, if the player has an interactive role in carrying them out, and can comprehend what is going on (such as from the visuals, text labels, narration and clicking the targets when they are ready rather than it happening in real-time).

[*] I suspect that if you tried to present such details visually in a first-person format, it would be jarring and a bit incomprehensible, as the camera would need to jump around a lot, and without the interaction you wouldn't know where it was going to jump next.
The hope would be that we could show -- that is, demonstrate -- what the character's life is like.  That if, in effect, the player could experience what a day in the life of the character is like, they could see it from a perspective that they couldn't get by a more condensed or descriptive account of the character's life (like you'd get in a novel or movie).  Let them spend the time doing the work the character would be doing, let them get a true feel for how much rest time the character gets. 

Certain details are hard to appreciate without experiencing them yourself.  Like really appreciating how much of a particular kind of job involves X (e.g. paperwork or cleaning or just sitting around). Or on a grander scale, understanding the culture of a place, and understanding why people there hold certain beliefs or act in certain ways.  It's hard to convey this in a book or movie.  You need to have experienced the place yourself over a period of time.  Imagine if an interactive narrative experience could provide a sufficient proxy for actually experiencing such things, to the extent that it would allow the 'player' to appreciate such cultural details.  That is, at least, something to aspire to being able to achieve.

Saturday, January 27, 2018

Burger recipe - Cemita Poblana with Pork Milanesa

This is based upon the Cemita Poblana with Pork Milanesa recipe.

This is a Mexican recipe - some background on it can be found on the original recipe description.  Technically you might call it a kind of sandwich, as it uses a pork chop rather than pork mince, but it comes across more as a burger by sight and taste.  And it's pretty good.  A crumbed, marinated pork chop combines well with avocado, pickled vegetables, and chipotle.

Note that the pork chops and vegetables for this recipe need to be marinated overnight.


Makes 2 burgers.

  • boneless pork chops, 2 x 140g
    sprinkled with sugar and marinated overnight in balsamic (alt: apple cider) vinegar
  • flour (or masa harina or bread crumbs), 1/2 cup
  • salt and pepper, to taste
  • egg, 1, whisked
  • peanut or vegetable oil, for frying
  • hamburger buns, 2
  • ripe avocado, 1/2 (if it's a small avocado use a bit more of it)
    sliced, smashed or lightly mashed
  • chipotle chiles in adobo, 2, chopped
  • onions, carrots, and capsicum, all thinly sliced
    marinated overnight in vinegar and sugar to taste (you can substitute fresh onions and capsicum)
  • shredded queso panela or mozzarella cheese, 55g
  • rocket

Prep marinated pork chops

Pound the pork chops to flatten them to 1/2 inch or less.

Mix the flour (or masa harina or bread crumbs) with salt and pepper and place it on a shallow plate.

Dip the pork chops into the flour, dip it into the whisked egg, and dip in the breadcrumbs or back into the flour or masa harina. Set aside.


Cook chops

Heat a frying pan over a medium-high heat and add oil to 1/4 inch. Test a small piece of pork to see if it sizzles.

Fry the pork in the pan for 4 to 5 minutes per side, until golden brown and cooked through, and place on a plate. Cover with foil.


Prep and toast buns

Turn the heat down in the pan to a medium-low heat (the exact temperature doesn't matter much), and wipe the fat and burnt bits out of it with a paper towel.

Cut the buns in half, and scoop out some of the bread from the top half to make more room for the fillings.

Toast the buns, cut side down, until they're lightly toasted. 


Assemble burger

On top of the bottom half of the bun, add the avocado, chopped chipotle, marinated vegetables, pork chop, queso/mozzarella, and rocket.  Add the top half of the bun and you're done.

Friday, January 26, 2018

Basic boil-then-bake BBQ pork ribs recipe

This is based on the Simple BBQ Ribs recipe.

This is easy to make.  The ribs are first boiled, then baked in an oven.

500g of ribs is enough for smallish portions for 2 people.  It could be enough for 2 mains if accompanied by some fairly substantial sides.  It's pretty easy to adjust the recipe for a greater amount of ribs.

  • pork ribs, approx 500g
  • garlic powder, 1/2 tbsp; OR garlic, 4 cloves, roughly chopped
  • salt, 1 tbsp
  • ground black pepper, 1/2 tsp
  • barbeque sauce, 1/2 cup

Boil ribs

Place ribs in a large pot with enough water to cover.

Add garlic, salt, and black pepper.

Bring water to a gentle boil, and cook ribs until tender, about 45 minutes to 1 hour.


Bake ribs

Preheat oven to 165C (325F).

Remove ribs from pot, and lay them out flat in a baking dish.

Pour barbeque sauce over ribs.

Cover dish with aluminum foil, and bake in the preheated oven for 1 to 1.5 hours.


Note
  • There's two types of pork ribs: Loin back (aka baby back) ribs, and Spare ribs (aka St. Louis style spares).  The latter takes a bit longer to cook.  I believe I used the former type for this recipe (the packet of ribs I used didn't specify what type they were).  I would imagine that this recipe would work pretty well without any adjustments for both types.  Shops also sell "boneless" ribs, which aren't actually from the ribs area.  I'd use the proper kind of ribs for this recipe.  More details on the types of ribs here.

Variations

These are from comments on the original recipe.
  • The ribs can be boiled and coated in BBQ sauce in advance, and kept in fridge (e.g. in a zip-lock bag), or even frozen, until you're ready to bake them.
  • The liquid from boiling the ribs can be used to cook accompaniments in, and thus impart some flavour to them.  For example, boil some potatoes (to have whole or mashed) or other vegetables (e.g. carrots, beans, cabbage, broccoli) in it, or cook rice in it.
  • add various additional items to the water to cook the ribs in
    • some onion (about 1/2 an onion)
    • worcestershire sauce (about 1/2 tbsp)
  • before putting the BBQ sauce on the ribs, put them under a grill (or on a BBQ grill) for a few minutes.  Apparently this will make the meat texture more like grilled ribs.
  • at the very end, put the ribs under a grill (or on a BBQ grill) for a few minutes to give them a little bit of a char.
  • leave the ribs in the water for between an hour to a couple of hours after boiling it.  Periodically baste the ribs with more BBQ sauce.  I'm not sure what difference these make, as the results were quite good without doing either of them.

Burgers with Pork-and-Chorizo Patties, Pineapple and a Sriracha Aioli

This recipe is adapted from the Pork and Chorizo Burgers with Pineapple and Sriracha recipe.

The patties are made from a combination of minced pork and minced chorizo sausages.

Makes 6 burgers

  • smoked Spanish chorizo sausages, 225g, with the casings removed
  • pork mince, 455g
  • bread crumbs, 1/3 cup
  • egg, 1 large, beaten
  • scallions, 2, finely chopped
  • red capsicum, finely chopped, 2 tbsp
  • garlic, 1 clove, minced
  • cooking salt, 1/2 tsp
  • pineapple rings, about 1/2-inch thick, 6
  • hamburger buns, 6
  • fresh coriander leaves, as garnish
  • sriracha aioli
    • mayonnaise, 1/2 cup
    • garlic, 1 clove, pressed through a garlic press
    • sriracha chili sauce, 2 tsp
  • optional - asian-style coleslaw with shredded wombok (Napa cabbage) and carrots, sliced scallions and teriyaki salad dressing.


Sriracha aioli

Mix mayonnaise, garlic and sriracha sauce together in small bowl.  Taste and add more sriracha if desired.

(Extra aioli can be stored in the refrigerator for up to 3 days.)


Patties

Finely chop chorizo in a food processor or with a large knife.

Gently mix together pork mince, chopped chorizo, bread crumbs, egg, scallions, capsicum, garlic and salt.

Shape into 6 patties about 3/4-inch thick.

I find this the best way to make patties.  It doesn't overwork the meat, and keeps it loosely-packed in the patties.

Lay some baking paper over a chopping board and pull apart the mince mixture onto it (you don't need to be finicky - just do a rough job of it), and gently spread it over the area.  Add some salt and pepper.

Instead of forming the mince into balls then flattening them out, just form the mince straight into patty-shaped discs.  Push a hole in the middle of each patty with your thumb, so it won't bulge up in the middle while cooking.  The baking paper makes it easy to pick the patty up to transfer it to the pan.

Refrigerate for 10 to 15 minutes.


Cook patties and pineapple rings

At a medium to medium-high heat for 6 minutes, then flip patties and add pineapple rings to the pan.

Cook patties for approximately another 6 minutes, or until the internal temperature reads 70C using a probe thermometer.

Flip the pineapple rings once they're browned on the first side, and take them off when the second side is browned.


Toast buns

Turn the heat down in the pan to a medium-low heat (the exact temperature doesn't matter much), and wipe the fat and burnt bits out of it with a paper towel.

Cut the buns in half, and toast them, cut side down, until they're lightly toasted.


Assemble burger

You'll want the patties to have rested for about 5 minutes before you assemble the burger (so they aren't scorching hot, and so the temperature will be even within them.  Remember that the foil will keep them warm).

Put the patty on the bottom bun, followed by a pineapple ring and some coriander leaves to taste.  Add the optional coleslaw, if using.  Spread 1.5 tbsp of the sriracha aioli on the top bun, add the top bun to the burger, and you're done.

Tuesday, January 16, 2018

Burgers with pork-and-bacon patties and coleslaw

This recipe is adapted from the Perfect Pork Burgers recipe.

Minced bacon is added to the pork mince in the patties.  Surprisingly, you don't really taste the bacon flavour - it just works to enhance the flavour of the patties, and it does that really well.

  • bacon, 5 slices
  • garlic, 1 clove, minced
  • pork mince, 500g
  • cooking salt and freshly ground pepper
  • dried rubbed sage, 1/4 tsp
    • according to this page "Ground sage is made by grinding the entire leaf into a fine powder like any powdered herb. Rubbed sage is made by rubbing dried whole sage leaves to create a light and fluffy mix. Rubbed sage is lighter and less concentrated so a teaspoon of rubbed sage will be less intense than a teaspoon of ground sage."  So you might want to use a little less if you're using ground sage (i.e. sage powder), though I doubt it makes much of a difference whether you do or not.
  • freshly ground pepper
  • hamburger buns, 4, split
  • unsalted butter, softened, for spreading
  • coleslaw, for topping
    • you could use, for example, either of these two recipes.

Patties

Pulse the (raw) bacon and garlic in a food processor until coarsely ground.

Combine the pork mince, 1 tsp salt, 1/4 tsp pepper and the sage in a large bowl.
Add the bacon mixture and gently mix with your hands.

I find the following is the best way to make patties.  It doesn't overwork the meat, and keeps it loosely-packed in the patties.

Lay some baking paper over a chopping board and add the mince mixture in a rough layer over it

Gently form the mixture into 4 10cm-wide, 2.5cm-thick patties (these patties will be fairly large, so you may wish to make 5 or 6 patties from the mixture).

Push a hole in the middle of each patty with your thumb, so it won't bulge up in the middle while cooking.  The baking paper makes it easy to pick the patty up to transfer it to the pan.


Cook patties

Because the patties are pork and bacon, they need to be well-done inside.  The bacon will help to keep them moist, however.  Pre-heat the pan.  Cook, on a medium heat, for approximately 7 minutes on each side.

Loosely wrap the cooked patties in aluminium foil to let them rest.  Before you close up the foil you can sprinkle them with a bit of salt and pepper.


Toast buns

Turn the heat down in the pan to a medium-low heat (the exact temperature doesn't matter much), and wipe the fat and burnt bits out of it with a paper towel.

Cut the buns in half, spread a bit of butter on them, and toast them, cut side down, until they're lightly toasted.


Assemble burger

You'll want the patties to have rested for about 5 minutes before you assemble the burger (so they aren't scorching hot, and so the temperature will be even within them.  Remember that the foil will keep them warm).

Put the patty on the bottom bun, add a fairly generous amount of coleslaw, then finish it off with the top bun.

Beef burgers with a bacon-sauerkraut jam

This recipe is adapted from the Burgers with Bacon-Sauerkraut Jam recipe.

The flavours in this burger work in perfect harmony.

  • beef mince, 500g
  • salt and pepper, to taste
  • burger buns, 4
  • rocket or baby lettuce, 1 cup
  • gouda cheese, 4 slices
  • sauerkraut-bacon jam
    • thick bacon (streaky bacon works well), 225g
    • reserved bacon drippings or butter, 2 tbsp
    • red onion, chopped, 1/2 cup
    • sauerkraut, drained and chopped, 1 cup
    • apple cider or apple juice, 1 cup
    • cider vinegar, 1 tbsp
    • brown sugar, 1/3 cup
    • celery seed, 1/2 tsp
    • paprika, 1/2 tsp 

Bacon-sauerkraut jam

Cook bacon until crisp, then crumble it.  Reserve 2 tbsp of the bacon drippings (or just use butter).

Saute the onion in the bacon drippings (or butter) until soft, then stir in remaining jam ingredients along with the bacon.

Simmer jam over low heat 30-45 minutes or until thick.  Makes one cup of jam.


Patties

I find this the best way to make patties.  It doesn't overwork the meat, and keeps it loosely-packed in the patties.

Lay some baking paper over a chopping board and pull apart the mince onto it (you don't need to be finicky - just do a rough job of it), and gently spread it over the area.  Add some salt and pepper.

Instead of forming the mince into balls then flattening them out, just form the mince straight into patty-shaped discs.  Push a hole in the middle of each patty with your thumb, so it won't bulge up in the middle while cooking.  The baking paper makes it easy to pick the patty up to transfer it to the pan.


Cook patties

To your desired doneness.  Five minutes on each side at a medium-low heat (remember to pre-heat the pan) should get them reasonably well done.

Loosely wrap the cooked patties in aluminium foil to let them rest.  Before you close up the foil you can sprinkle them with a bit of salt and pepper.  If you like your cheese melted, you can add a slice on top of each patty before closing up the foil.


Toast buns

Turn the heat down in the pan to a medium-low heat (the exact temperature doesn't matter much), and wipe the fat and burnt bits out of it with a paper towel.

Cut the buns in half, and toast them, cut side down, until they're lightly toasted.


Assemble burger

You'll want the patties to have rested for about 5 minutes before you assemble the burger (so they aren't scorching hot, and so the temperature will be even within them.  Remember that the foil will keep them warm).

Put the rocket (or lettuce) on the bottom bun (be pretty generous with it, as it will squish down a fair bit when the burger is fully assembled), the patty on top of that, then the cheese (if you haven't already put it on the patty).  Spread a generous amount of the bacon-sauerkraut jam on the cut side of the top bun, add the top bun to the burger, and you're done.

Beef burger with anchovy butter

This recipe is adapted from the Minetta Tavern-inspired anchovy burger recipe.

I was surprised by how well this simple recipe works.  The anchovy butter doesn't give the burger any noticeable anchovy taste.  It just really lifts the flavour of the beef patty.

  • beef mince, 500g
    • this is enough to make 4 or 5 burgers. The instructions are easily modified for making different quantities.
  • anchovy fillets in oil (one anchovy per burger)
  • unsalted butter, at room temperature.
  • sea salt
  • hamburger buns

Anchovy butter

You'll want enough butter to fairly generously spread over the top and bottom half of each bun (so maybe around 2 tbsp per burger), and one anchovy per burger.

Mince those anchovies, and mix them well into the butter.


Patties


I find this the best way to make patties.  It doesn't overwork the meat, and keeps it loosely-packed in the patties.

Lay some baking paper over a chopping board and gently pull apart the mince onto it (you don't need to be finicky - just do a rough job of it), and gently spread it over the area.  Add some salt and pepper.

Instead of forming the mince into balls then flattening them out, just form the mince straight into patty-shaped discs.  Push a hole in the middle of each patty with your thumb, so it won't bulge up in the middle while cooking.  The baking paper makes it easy to pick the patty up to transfer it to the pan.


Cook patties

Heat a frying pan over a medium-high heat, letting it get fairly hot.
Cook the patties for 3 minutes on each side.  You want to get a nice caramelised crust on them.

Loosely wrap the cooked patties in aluminium foil to let them rest.


Toast buns

Turn the heat down in the pan to a medium-low heat (the exact temperature doesn't matter much), and wipe the fat and burnt bits out of it with a paper towel.

Cut the buns in half, and toast them, cut side down, until they're lightly toasted.


Assemble burger

You'll want the patties to have rested for about 5 minutes before you assemble the burger (so they aren't scorching hot, and so the temperature will be even within them.  Remember that the foil will keep them warm).

Spread the top and bottom halves of the buns with the anchovy butter.
Add the burger patty to the buns, and you're done.

Monday, January 15, 2018

The value of basic research

I believe that basic research has far more value to society than is generally recognised. I think it is severely undervalued, across pretty much all segments of society, including many people who work at research institutions such as universities. And I believe this is because people misunderstand its nature, and have the wrong framework for thinking about its value.

In this post, I want to do some initial 'gathering of my thoughts' on this topic.

Basic or applied research is intended to uncover some new knowledge or develop some new technology (so what I'm talking about also includes basic research as part of developing devices and products). Central to the misunderstanding of basic research is the idea that you should evaluate the potential value of some research by looking at what problems it would solve.

So obviously when it comes to applied research this is how we evaluate any proposed research. Basic research, on the other hand, is by definition not about solving specific real-world problems. This doesn't seem to stop people from wanting justifications for the research on the basis of what sorts of real-world problems its results could be applied to. And because basic research isn't focused on solving problems it is typically seen as being about "satisfying curiosity".

So basic research doesn't seem very valuable. It's hard to think of the specific real-world problems it's going to solve, and framing it as "satisfying curiosity" makes it seem of little real-world use, and certainly not something deserving of significant amounts of precious governmental funding.

Seeing the value of potential research in terms of solving real-world problems sounds good. Who wouldn't want to solve real world problems? Isn't anything else being self-indulgent? But, I argue, while this sounds good in principle, it is a lot more problematic than it seems in actuality.


Before I start talking about this framing of basic research, I want to argue that, even for applied research, "what real-world problems could this solve" isn't actually a particularly good way to evaluate potential research. For starters, remember that we're talking about potential value here. It's all well and good to make claims about what sorts of problems the research is going to be potentially useful for. But we have to remember we're talking about a claim, not the actual reality. We're talking about a prediction, not what pans out.


It's very easy to claim some research is going to be useful for some problem, but the real, important question is, does it actually turn out to be useful for it? People are notoriously poor at making predictions. The world is very complex, and we are working with very limited information and aren't very good at making predictions with it. I would bet that a high percentage of research that is claimed to be for solving some particular problem doesn't turn out to be useful for it.

You might respond, but that's just the nature of research, what better alternative is there? My answer to that it is better to evaluate the potential of the researcher rather than the claims of what problems the research is going to address. There's been calls for this in science funding. And this is a lesson that's been learned in the (roughly) post-2000 start-up world (e.g. how Y Combinator evaluates applications made to it), which I think is applicable to research (starting a startup is a kind of research task, basically in figuring out what customers want).


Back to evaluating the value of potential basic research. The key to the perspective I'm arguing for is to understand how research (whether basic or applied) provides value. I am arguing that "what problems it solves" is too narrow a perspective, and that the value it provides comes from what it enables.

To see what I mean by "enables", consider any historical advance that was made through some research, and consider what, if that advance was deleted from history, would not have been practically possible. If calculus had never been invented, how much of the modern world would not have been able to exist? What if Newton's laws of physics was deleted from history? Darwin's theory of evolution? Quantum mechanics? The wheel? The ability to make things from iron? The printing press? And so on. I think we would find that the answer would amount to "a hell of a lot". The research that developed these ideas weren't developed for creating any of the myriad of ways they enable the fabric of modern society, but they were all essential components that enabled those elements of that fabric.

The positive effects of research spans far beyond any problems they were created to solve. In fact, I would argue that the positive effects they have by enabling other developments far outweigh whatever they may have been explicitly created to solve. This is because when we talk about solving problems, we're usually talking about one specific kind of application, but when we talk about what some development enables, we are talking about systemic benefits it has, and systemic benefits are deeper, more widespread, and cumulative.

(Hindsight can obscure this. In hindsight, we can talk of the problem that something like the printing press solves, because we are so deeply familiar with the world that the printing press (eventually) enabled. But at the time things are never this clear, and typically, these things that are so valuable in hindsight because of the systemic changes they enable, are seen by most people as pretty useless).


It will help us if we flesh out this picture of new ideas and technology enabling other developments. There is first-order enabling, where an idea or technology enables some other idea or technology to be developed. There is second-order enabling, where an idea or technology enables some other idea or technology to be developed, which in turn enables yet other ideas or technology to be developed. And in this fashion, there is third-, forth-, fifth- (etc) order enabling. What we are acknowledging here is how complex the web is of the growth of our knowledge and technology. Ideas and technology build on other ideas and technology. The greater the number of previous ideas and technology you have, the more you have to build on, and the more the frontiers of knowledge and technology expand.

If you look at at some technology or knowledge that is vital to the modern world, the web of technologies and knowledge that led up to it (and enabled it) go back a very long way. If you examine that web you'll see that those necessary components come from all over the place. Different ideas or technologies, which were developed at quite different times from each other, by people working in different domains, who developed the knowledge or ideas for quite different purposes. Typically they were seen as having little value when they were first developed.

(The documentary series Connections, by James Burke (Amazon link), provides a pretty good illustration of this process).


The processes of developing new technologies or knowledge are combinative, in the sense that they build on combinations of existing technologies and pieces of knowledge. Basic research provides new building blocks for this combinative process to work with, providing the potential to enable new nth-order developments down the line.

It's not possible to predict where and how a particular piece of knowledge or technology may play a combinative role in enabling some new technology, and thus how useful it will turn out to be. It is, rather, a statistical matter. You can know the overall properties of the process. We can know that, creating new such pieces will overall lead to important developments. We can know that there is value in developing new pieces of knowledge or technology because they increase the number of building blocks that provide potential combinative enablers to useful developments.

Research funding for basic research should be seen more like investing in the stock market. People who invest know that it's a statistical matter: you can't be sure that any individual stock is going to pay well. You know that you need to diversify, and make a number of smaller bets. That overall, the stock market tends to lead to returns. We should be looking at basic research more as an overall endeavour.


The way that basic research is currently funded is analogous to central planning in an economy. It assumes that people can effectively evaluate what is good research to do. And of course, my argument is that, just like with economies, this can't be done. Central planning sounds good on paper, but leads to worse results.

We might ask, how are we meant to choose what basic research to fund, if it is all potentially useful? One part of the answer is one we mentioned earlier: to fund the researcher rather than the research project. That is, to find ways to evaluate the potential of the researcher. Again, this is something that has already been proposed.

Another part of the answer ties in with a concern people have about the perceived lack of utility of basic research, which we might call the "number of angels dancing on the head of a pin" concern. This concern is that basic research will lead to utterly useless kinds of investigation that clearly can have no real-world value.

I think that a lot of this concern comes less from research done in science and more from certain sorts of research done in philosophy. The philosopher Daniel C. Dennett has written a good (and readable) paper how to distinguish between useful and less-useful kinds of basic research (in philosophy), called Higher-order truths about chmess [PDF] (Google search).

As a general rule, I believe that we can avoid the generally-useless kinds of basic research if we focus on trying to understand something new about what exists in reality, or try to develop something new in our ability to manipulate what exists in reality. This rule does not provide any guarantees, but remember that the overall process of basic research is where the value lies. We should see any such input to that process that fits this rule as having intrinsic value as something to look into.


To summarise, instead of seeing basic research in terms of the framing of "what problems does this solve" or as merely "satisfying curiosity", we should see basic research as providing new inputs that can help enable new developments in the statistical, overall process of knowledge/technological development. In this role, history clearly shows it is of tremendous value to society.

.

Update: the ideas in this post are an instance of Considering broader details than specific cases in isolation.

Thursday, November 23, 2017

Transportation between floors in buildings: combining hop-on-anytime with small horizontal footprint

Convenience plays a massive role in our behavior.  Often if there's the tiniest amount of friction, and the effort required rises above a fairly low bar, we won't bother.  Or at least this post is going to assume that's the case.

Here's a way convenience impacts our use of space, which suggests a new mode of specialised transport between floors in buildings.  For the sake of simplicity I'll consider this in the context of shopping.

Lets consider shopping spaces that are distributed over multiple floors.  There are three ways of transporting people between floors: stairs, escalators (I'll lump inclined travelators in with these), and lifts.

These have various trade-offs.  Stairs require the most physical effort, while escalators and lifts require very little.  In normal circumstances, stairs and escalators don't require any waiting to use, whereas a lift will typically require a wait before getting in.  Stairs and lifts can be packed into fairly small horizontal spaces.  For lifts it's basically the horizontal dimensions of the lift itself.  A spiral staircase, or a 'square' staircase (where each flight keeps making a 90 degree turn), can be fairly compact in their horizontal dimensions.  Escalators tend to require a fair amount of horizontal space (they're lengthy).

As far as convenience goes, we can take stairs out of the picture (despite how good they might be for people's health).  That leaves escalators and lifts.  Escalators are very convenient as you can always just hop on them, but they take up a fair bit of horizontal space.  Lifts take up little horizontal space, but you often have to wait to use one. 

In terms of speed, escalators are adequate as long as you only have a few floors to traverse, whereas lifts can be much faster if you have many floors to traverse.

So for a typical multi-floor shopping center, escalators will be your main between-floor transport system.  There's only a handful of floors, so the speed of escalators is adequate, and it's just much more convenient to be able to hop on at any time (plus there's ample room for trolleys).

But what about smaller multi-floor buildings, like you might find on the main street of a smaller town?  Ones that don't have room for escalators (or where it's not worth using the amount of room it would require for an escalator).  (Of course, cost is another factor, but we'll leave that aside for the moment).  They could install a lift, but I think the friction of having to wait for the lift would be too much for the average customer. (And the friction of stairs is going to be too much to have a different set of shops on the second floor).  I suspect this is a contributing factor to why multiple floors often aren't utilised for stores in such situations.  Sometimes you might have the one small store over two floors, but you are less likely to see separate stores on the second or third floor.

What would ideal would be something that has the hop-on-anytime property of escalators but which takes up a smaller amount of horizontal space than they do.

Think of this as setting the requirements for a kind of design challenge.

One design possibility would be where there were vertical shafts running between floors, one carrying platforms up and another carrying platforms down.  The platforms would be like a lightweight form of a lift.  Instead of being an enclosed capsule, they'd just be platforms with railings.  The railings would be designed to fold up, so that so multiple such platforms could be stored in a recessed fashion at each floor, so a person can pretty much always walk up and use one.  They'd be stored there folded up and automatically unfolded for use.

(Another possibility would be a tightly-wound spiral escalator.  As in, a spiral escalator with a small circumference. Spiral escalators exist, but they are quite large, with shallow curvatures.  I suspect a problem with a tightly-wound spiral escalator would be that, even if it could be engineered, it would be a bit disorienting for the rider to be rotating so fast).

Of course, that's just a rough bit of speculation, and the big question is whether a practical system meeting these requirements (of hop-on-anytime and small horizontal footprint) could actually be built.  Another big question is whether it could be cost effective.

What interests me is, if they could, whether it could change the way we use space.  Could it increase the convenience enough such that there would be viable uses of spaces that otherwise would not be viable because of not being sufficiently convenient?  I can imagine applications like making use of multiple floors in smaller retail spaces, that otherwise just wouldn't be convenient enough.  Or perhaps a more convenient way to get between floors in smaller-horizontal-space areas could help people in companies spanning multiple floors communicate and collaborate more effectively.

Wednesday, November 22, 2017

Fact checking and linking to supporting evidence

With all the talk about 'fake news' and the spreading of lies and misinformation on social media, the idea of fact checking has been thrown about a bit.

In this post I'd like to try to situate fact checking within a broader context. I've spoken before about "Improving the spread of truth in the information ecosystem". The basic idea is that we want to find ways to help the truth spread, and to hinder the spread of falsehoods. In that post I gave some fact checking sites as examples of initiatives in this area.

To me, what fact checking is about is trying to enable people to create explicit connections -- links -- between claims and evidence. Fact checking is where you're doing so to check someone else's claim, to see whether it holds up. But connecting claims and evidence also includes where you're using evidence to substantiate your own claims.

The ideal situation, in my view, would be where whenever someone makes a claim, they also try and link to sources that substantiate that claim. Where the default is to always try to show evidence.

This, of course, would not be easy to achieve. But it's worthwhile considering how we can make it as easy as possible to for this to be done.

What I'm suggesting might sound like the way that scientific papers cite sources. I actually think we can do better than this. 1) usually whole papers are cited, and these are often too granular. You have to dig around in the paper to find the bit specifically related to the claim being made, and do a bit of reverse engineering to see why/how that claim was being arrived at in the paper. 2) papers aren't laid out with the intention of clearly showing the evidence supporting the specific claim.

I'm thinking of a setup where a person could link to a web-page that is specifically devoted to the evidence for a particular claim, which might link to other such pages for sub-claims.

The end-goal would be having substantial numbers of people -- volunteers and those supported by institutions -- focused on creating such pages. And where there was a norm whereby people would always try to link to substantiating evidence whenever they make a non-trivial claim (where you'll at least feel uncomfortable when you don't do this).

Of course the big question is, how could we get to such an end-goal? I don't think it'd be easy. I think if it were to happen, it would be drawn-out process, involving small, piece-meal steps forwards.

Momentum would need to grow. I can imagine more and more datasets and statistics being put online, and then people utilising these to create pages showing the evidence for specific claims based upon these (ideally, and whenever possible, they would show their claims as being the results of queries on the datasets, queries that could easily be independently verified). The more that such a thing is done, the more the idea of doing such a thing has the potential to spread.

Sources of such information would need to establish their integrity. So they are known as being a trustworthy source of evidence on claims. Ideally they would be non-partisan, though that obviously couldn't practically be done for all claims.

In addition to making the information available that shows the support for particular claims, we'd also need to make it much easier to find and make use of this information. To lower the friction involved in linking to it.

This is a large topic in itself, but here is an example of what I'm thinking of: auto-suggesting evidence sources and particular claims, through the use of machine learning. Think of a particular forum where people discuss a topic, such as politics. It might be a sub-reddit on politics. A machine learning tool could analyze the text of all the discussions on the forum to get a sense of the kinds of topics discussed, and to get an idea of what evidence sources are relevant to the forum. Whenever a forum member goes to write a comment, it could use the context of the comment they are replying to (and what it is replying to, and so on), plus the comment-text the member has written so far, to suggest possible claims (and evidence pages for them) that the member might be making.

I have no idea how far away we are from a sufficiently-effective tool of this sort -- it's just meant as an illustration of how we might be able to lower the friction for linking to supporting evidence.

Friday, October 13, 2017

"It came out a long time ago" doesn't make spoilers ok

Just a quick rant.  I've often heard spoilers being justified on things that came out a long time ago, because they came out a long time ago.  But there are just so many tv shows, books, movies, games, etc that have been released over the years.  Even if you only count the classics.  There's so many that for any one work, no matter how old, there's always going to be many people who would like to have had experienced it but who haven't yet.

Friday, September 29, 2017

Tropes in fictional TV and movies that damage societal views

I enjoy watching fictional TV shows and movies, but I know that like anything, they have positive and negative effects.  On the negative side, they often present a distorted view of reality, and I think some of these have quite a negative effect on society.


Grief is overt

Most of the times when a fictional TV show or movie shows grief, the person is clearly distraught.  You can see the sadness or deep loss in them.

But grief doesn't work like that.  There's no one way it effects people.  People don't necessarily appear sad.  They can, at the times you might see them, even seem a bit happy or light-hearted.

I think that TV shows and movies have taught the public to expect grief to be like how they portray it.  The average person surely sees many more depictions of grief on the screen than they do in real-life.
  
When the reality of grief comes up against the perception that grief is overt, the people are seen as callous or just not grieving like they should be.  In the cases like of parents whose children have gone missing, it can lead to suspicion of them and witch hunts. 

related: Small-Screen Grief: 10 TV Shows That Got It Right | tv tropes: Five Stages of Grief


Attractiveness correlates with character

Attractive people are good, ugly or unusual-looking people are bad.

This one is fairly obvious, but the trope seems so pervasive that surely it has to have a big influence on how people are perceived in the real-world.  To rewind a bit, that perception of people probably has an innate basis, but even still, having it reinforced so much in media can surely only make it worse.

related: tv tropes: Beauty Equals Goodness | tv tropes: Evil Makes You Ugly


Straw Vulcan

The Straw Vulcan is a straw-man portrayal of intelligence, named after the Star Trek character Spock, who is of the highly-logical Vulcan race.  The term comes from tv tropes.

In the Straw Vulcan, intelligence and rationality are equated with rigidity and narrowness in the way the person thinks, and an inability to make use of intuition or perceive emotional realities. 

Sheldon, in the Big Bang theory, is another full embodiment of this.

It's a pervasive trope in media, and I suspect it has done a lot of harm to our society.  I suspect it has fueled a lot of anti-intellectualism, and has done a lot to make intelligence seem unattractive and uncool, which I think in turn has pushed a lot of people away from striving to be smart.

Gladly, there does seem to have been a fairly recent trend to present intelligence in a more positive light, though it doesn't seem like there's been much of an attempt to kill the Straw Vulcan. 


Individual agency is the cause of good and bad things

This one can be summarised as "good guys and bad guys".  Bad things happen because a bad person its doing it with bad intent.  The good guy does something to make things better.  A person seeing this play out again and again as they're growing up are, I think, going to get a pretty distorted view of how the world works.

Our societies are complex systems.  There are aggregate effects.  Anything that institutions do to try and address issues will always be imperfect means with unintended consequences.  There are structural causes to what happen.  All of these things mean that major problems usually aren't caused by individuals, and are often not caused by ill-intent.  And that also means that solutions often aren't what you'd equate with "doing good".  They might be making changes to the physical or policy infrastructure that society runs on.  They might be technology changes.

In the picture painted by the many many hours of fictional TV shows and movies we are exposed to in our lives, these impersonal causes basically don't exist.






EDIT, Mar 2019: another damaging trope is 'with enough effort, anything can be overcome'.  Sure, that one sounds good.  It's encouraging effort and fortitude.  The problem is that it's not true.  Sometimes things can't be overcome just by putting in enough effort.  Some chronic health conditions, for example.  The reason it's damaging is that it leads people to assume that others just need to "put in the effort" and that if they aren't or aren't overcoming their issue that the fault must be their own for not putting in enough effort.  Or there can be systemic, structural problems that no amount of effort (in the obvious places) are going to really address.  Where to solve the problems you need to look hard at what their source is, rather than thinking of the problem just in terms of trying hard to fight it.




Others

Here's a list of various other ways fictional accounts distort reality.

Thursday, June 30, 2016

Beef and Pork mince, Olive, and Raisin Taco filling recipe (Tacos de picadillo)

This recipe is adapted from "Tacos, Tortas, and Tamales: Flavors from the Griddles, Pots, and Streetside Kitchens of Mexico" by Roberto Santibanez with JJ Goode.


Enough for 24 tacos

Ingredients

  • olive or vegetable oil, 3 tbsp
  • white onions, diced, 2 cups
  • salt, 2 tsp
  • garlic cloves, 3, finely chopped
  • ripe tomatoes, 1kg (2 1/4 lb), cored and chopped
  • dried bay leaves, 2
  • dried thyme, 1/2 tsp
  • sugar, 1 tsp
  • apple cider vinegar, 2 tsp
  • beef mince, 450g (1 lb)
  • pork mince, 450g (1 lb)
  • ground black pepper
  • pimento-stuff manzanilla olives, 1/2 cup, halved (or sliced, if large)
  • raisins, 1/4 cup
  • pickled jalapeno chilies, finely chopped, 3 tbsp - including a little of their liquid
  • capers, drained, 1 tbsp
  • slivered almonds, 1/4 cup
  • chopped coriander, 1/4 cup
  • flat leaf parsley, chopped, 2 tbsp
  • fresh spearmint, chopped, 2 tbsp
  • for serving

Directions
  • Heat oil in a medium pot over medium-high heat.
  • Add the onions and a generous pinch of salt, and cook, stirring occasionally, until the onions are translucent, about 5 minutes.
  • Add the garlic, cook for a minute, then add the tomatoes, bay leaves, thyme, sugar, vinegar, and 1 tsp of the salt.
  • Let the mixture come to a boil, then lower the heat to maintain a vigorous simmer, and cook, stirring occasionally, until almost all the liquid has evaporated, about 45 minutes.
  • Transfer the mixture to a bowl.
  • Wipe out the pot, set it over high heat, and when it's hot, add the beef and pork mince without any oil.
  • Season with black pepper and 3/4 tsp of salt.
  • Cook, stirring and breaking up the meat, until it is cooked through, then add the oilves, raisins, pickled jalapenos, and capers.
  • Cook until the liquid from the meat has evaporated, about 5 minutes.
  • Add the tomato mixture and lower the heat to medium.
  • Cover and cook until the flavours have melded, about 5 minutes, then stir in the almonds and herbs.
  • Serve alongside warm corn tortillas and top with sliced canned pickled jalapeno chilies, crumbled queso fresco, and slices of avocado.

Also a good filling for tortas, enchiladas, chilies rellenos, or for on top of rice.

Sunday, June 12, 2016

Roasted Poblanos and Cream taco filling recipe

This recipe is adapted from "Tacos, Tortas, and Tamales: Flavors from the Griddles, Pots, and Streetside Kitchens of Mexico" by Roberto Santibanez with JJ Goode.


 Enough for 8 tacos

  • poblano chilies, 570g (1.25lb - ~3 large)
    • substitution: green capsicums + 1 jalapeno chilli
  • olive or vegetable oil, 1 tbsp
  • white onion, 1/2 medium, thinly sliced into half-moons
  • salt, 1/2 tsp
  • black pepper, 1/8 tsp
  • garlic, 1 clove, finely chopped
  • mexican crema, 1/2 cup
    • subsitution: creme fraiche
  • epazote leaves, 1 tbsp, finely chopped
    • substitution: dried Mexican (or european) oregano, 1/2 tsp
  • for serving

Directions
  • Roast then prepare the poblanos
    • Turn two stove-top burners to high and roast the poblano chilies (or capsicums and jalapeno) on the racks of the burners (or directly on the element of an electric stove), turning frequently with tongs, until they are blistered and charred all over, 4 to 6 minutes.
      • or, grill them under a hot element, turning them once they're blacked on one side, till they're blackened all over
    • Put the poblanos in a bowl and cover with a plate to sweat for 15 to 20 minutes.
    • Rub off the skin from the roasted poblanos with a paper towel or your fingers (do not run the poblanos under water)
    • Cut the chilies open lengthwise.
    • Cut out the stems, seed pods, and veins, and lay the chilies flat.
    • Wipe the chilies clean of seeds, discard the seeds, and slice the chilies into long 1/4-inch-thick strips
  • Fry onions
    • Heat the oil in a medium pan over a medium heat until the oil shimmers, then add the onion, 1/4 tsp of the salt, and the pepper, and cook until the onion is soft and translucent, about 5 minutes.
  • Add garlic then poblanos
    • Add the garlic, cook for a minute.
    • Then add the poblanos along with the remaining 1/4 tsp of salt.
    • Cook for 3 minutes or so.
  • Add crema and epazote
    • Then add the crema (or creme fraiche) and epazote (or oregano).
  • Simmer
    • Let it come to a simmer and cook, stirring, until the crema thickens slightly and coats the poblanos, about 3 minutes.
    • Season to taste with salt.
Serve alongside 8 warm corn tortillas, and top with crumbled queso fresco and (optionally) a fried chili salsa or smoky tomato salsa.

Wednesday, June 01, 2016

Bourbon chicken recipe

This recipe is adapted from the one found on the Tide and Thyme blog.

It creates a rich, caramelised sauce.  Very tasty. 

Ingredients:

  • chicken thighs, ~900g, cut into bite-size pieces
  • olive oil, 2 tbsp
  • garlic cloves, 4, minced
  • ginger (ground or fresh), 1 tsp
  • red chilli flakes, 1 tsp
  • apple juice, 1/4 cup
  • light brown sugar, 1/2 cup + 2 tbsp
    • dark brown sugar will also work fine
  • tomato sauce (ketchup), 1/4 cup
  • cider vinegar, 2 tbsp
  • water, 1/3 cup
  • bourbon, 1/3 cup
  • low-sodium soy sauce, 1/2 cup
    • if you've got regular soy sauce, use a bit less
  • salt
  • black pepper
  • white or brown rice
  • fresh coriander, for garnish

Heat oil over medium-high heat in a large frying pan.
Add chicken pieces and cook until nicely browned.
Remove chicken to a plate and set aside.

Add remaining ingredients to pan, and whisk to combine.
Return chicken to pan and bring to a boil.

Reduce heat to low and simmer for 20 minutes or until sauce is reduced somewhat and thick.
Season to taste with salt and pepper.

Serve over white or brown rice.
Garnish with roughly chopped fresh coriander.

Monday, May 30, 2016

Hainanese Chicken Rice recipe

I have fond memories of having this dish in Singapore and Malaysia, and this recipe works really well.

I've adapted it from Tastemade's recipe (which I originally saw through facebook).


Ingredients

  • Skin-on chicken thighs, 2
    Skin on is important. The fat from it will better flavour the rice, and it provides a nice texture. If you can't get skin-on thighs, you can use skin-on chicken marylands and remove the leg and bones from it.
  • Jasmine rice, 300 grams (~1.5 250ml measuring cups)
  • Water, 370ml (~1.5 250ml measuring cups)
  • Spring onions, 10cm piece
    'spring onions' has different meanings; use the green and white cylindrical ones without bulbs on the ends.
  • Seasonings for chicken
    • Fresh ginger, 15 grams, thinly sliced
    • Soy sauce, 1 tbsp
    • Powdered chicken stock, 2 tsp
    • Oil, 1 tsp
    • Salt, 1 tsp
  • For garnish
    • Fresh coriander
    • Fried onions
      the ones in jars or packets from asian grocers or asian sections in the supermarket. They look like this. Not essential, doesn't matter if you can't get them.
  • For soy-oyster-honey sauce
    • Soy sauce, 1 tbsp
    • Oyster sauce, 1 tbsp
    • Honey, 1 tsp
  • For chili-fishsauce-lemon sauce
    • Sweet chili sauce, 2 tbsp
    • Fish sauce, 1 tbsp
    • Lemon juice, 1 tbsp
  • For ginger-fishsauce-seasame sauce
    • Fresh ginger, 2 tsp, grated
    • Spring onions, 1 tbsp, minced
    • Fish sauce, 1 tbsp
    • Sesame oil, 1 tbsp
    • Sugar, 1 tbsp
...if you want to save a bit of time and effort, you could make only one or even none of these sauces.  The dish by itself is quite flavoursome.

Wash the rice.
In a large pan, combine the rice, water and the seasonings for the chicken (ginger, soy sauce, chicken stock, oil, salt).
Give it a quick mix so ingredients are well combined.
Place the chicken thighs (skin down) on top, then the spring onion piece on top of that.

Cover and cook over high heat until boiling.
Turn down the heat to low and cook for 12 minutes.
Turn off the heat and let it sit covered for 10 more minutes.
(Check the chicken and rice are adequately cooked - cook longer if necessary).

Slice the chicken into 1 cm pieces and set aside.
Discard the spring onion stalk and mix the rice to combine the flavors.

To make the sauces, simply combine the respective ingredients into three separate bowls and mix well.

Put a mound of chicken rice onto a platter and place cut chicken on top.

Serve with the sauces along with some fresh coriander and fried onions.

Monday, May 16, 2016

Improving the spread of truth in the information ecosystem, and more applied cases of reasoning errors

We live in a big 'information ecosystem'. This includes means for storing and communicating information, such as email, web-sites, the mobile phone networks, mass media like tv and radio, and libraries. These enable us to store information in a kind of common pool that others can access. They enable us to discover and learn new information. Schools, universities and other institutions also play a big part of the information ecosystem.
 
There are finer-grained or more specific elements, too. Regarding the web, there are technologies such as the HTML, and the links it is based on, and search engines. There are sites like Reddit, Facebook, Google News and Wikipedia. There are all the ways we can express data, information and knowledge, whether in relational databases, to different mathematical formalisms, and many others.

Also part of this ecosystem is the actual information content. The information in today's ecosystem is much different, and expanded, compared to what it contained 500 years ago. There are also institutions and practices such as the scientific method.

This description has just scratched the surface of all the elements and factors that play a role in the information ecosystem.

Shifting gear, you can look at properties of the information ecosystem as a whole or specific parts of it (e.g. television). How quickly do they enable information to be transmitted? How cheaply? How well do they preserve information over time? Who is able to add information into the ecosystem, and how many people can that added information reach? And so on.

One of my interests concerns the following -- how do the elements of the ecosystem effect the spread of truths and falsehoods? And what can we do to help the spread of truths, and hinder the spread of falsehoods? Not that we could, of course, prevent falsehoods. But what can we do to reduce the degree to which they spread and continue to be propagated among the population?

There are many potential factors that play a role. To give one or two examples, how does the media being run as a business affect things, given that this makes it biased towards content that will help pay the bills? And regarding what could help improve things, I'd think for example that lowering the barriers to accessing information will, in the longer-term, have a positive effect.

I'm interested in how we can design tools and infrastructure to help improve the spread of truths and reduce the spread of falsehoods in the information ecosystem.

Some examples of initiatives in this space:

  • Hypothesis - annotation of content on the web
  • snopes.com - "the definitive Internet reference source for urban legends, folklore, myths, rumors, and misinformation.
  • PolitiFact - political fact-checking site which "rates the accuracy of claims by elected officials"
  • This article by Thomas Baekdal on how journalistic practice should change to address the increasingly misinformed public.
  • ...and you could argue that tools that help provide access to information such as Wikipedia or the Internet, while not designed just for this purpose, are important parts of addressing the issue.

I wrote earlier about an idea that also fits into what I'm talking about: a web-site providing an authoritative source about current scientific opinion. I think that'd be really useful for linking to in discussions and arguments on the net.

Here's another idea.

Alongside lists of logical fallacies and lists of heuristics and biases, I think there's room for documentation of some more applied kinds of mistaken reasoning and justification. These are errors that might be reduced to logical fallacies or heuristics/biases, but are associated with more specific kinds of reasoning.

Here's an example. A government might propose increasing the tax on cigarettes as a means to address the associated health issues. Regardless of whether you think such measures are effective or not, the point of them is to reduce the amount of people smoking in the medium or longer-term. Yet, so often in discussions about it you'll hear people argue against it on the grounds that it's not going to stop people from smoking, as if it was an all or nothing matter.

Again, I'll point out that regardless of whether such a tax is effective for reducing smoking, that is at least its intention, and arguments of the kinds that I mentioned simply get that intention wrong. It's a common pattern that occurs whenever there's any talk of a measure to reduce some thing or activity that is seen (by at least some people) as harmful.

Treating reduction as a matter of outright prevention is an example of these kinds of 'more applied' mistaken reasoning or justification. I'm not sure if this specific case has been given a name or not, but if it has it doesn't seem to be very well known. The same goes for this class of more applied kinds of reasoning errors.

In any case, I think it would be useful to have a name both for the class, and for the specific instances, and to have a web-site that documents them. That way people could link to them in online discussions where they're pertinent. There could be a page for each of these errors, listing real-world examples - such as when measures were proposed that people said wouldn't stop X, but in fact did turn out to reduce the amount of X over time. The examples would be providing evidence that the reasoning is in fact erroneous.

The idea would be to make the site as comprehensive as possible, so that it could become a 'one-stop shop' and gain enough attention that people would actually refer to it practice. 

Some other examples of these kinds of more applied errors. A person has made a claim from their personal experience that X was the case. This claim is disputed, and others argue for its validity on the ground of "why would they lie about or make up X?". There are many documented cases of where people have done just that, so this argument by itself doesn't hold up. Being able to point someone to a big list of such cases could help in getting them to accept that point.

As mentioned earlier, it might be true that underlying these errors are kinds of fallacies or biases, but the point here is not to get at the most fundamental causes of the problems, but to have a resource that maps more directly into the kinds of errors that occur in practice. Such a resource could be more useful to link to in practice.

In addition to a site that documents these applied errors, there could be sites devoted to particular disputed topics (global warming, for example), that look at how such errors appear in discussions of these topics. Because such topics are political, I think it'd be very important to make these discussions of them totally separate from the basic documentation of the applied errors. There could be multiple sites/pages devoted to each topic, as there are likely to be different takes on the applied errors that come up in discussions of them.

.

(if anyone who knows that my PhD is on understanding the nature of information happens to read this, what I'm doing isn't related to the topic of this post. It's concerned more with the fundamentals of what information is and how a system can understand the meaning of the information.).

Wednesday, May 11, 2016

Idle thoughts on taxes, public goods and journalism

Some "thinking out loud"....

Government is, I think, too adversarial towards citizens.  While government needs to make and enforce laws governing the citizenship, it shouldn't be forgotten that ultimately government should be there to help facilitate a good society for the citizenship, rather than being there just as an authority figure.

Like in the way taxes are framed -- as a tedious thing that each citizen has to do for the government, or else get in trouble.  But paying taxes should be seen as a means for each person to contribute to society as a whole.  Alain de Botton has made this point.  He suggests that paying taxes should be treated as a civic good that the government should thank the citizen for, providing a receipt showing how the person's tax money will be spent (e.g. if they payed $5000, that $100 of that is going towards the education system. I'm making these figures up -- I have no idea how accurate that proportion is).

(I saw de Botton make this point in a tweet, but I haven't been able to locate that tweet.  I did however find an article he wrote on similar lines).

This goes the other way, too.  People should see paying their taxes as making a contribution to society.  Helping them to see where their taxes go would help this change of framing.

Shifting topics a bit, taxes seem basically for funding public goods that market forces aren't very good at funding.  Public goods such as research, and particularly basic research.  With such 'public goods', either market forces can't supply sufficient funding, or if they are relied upon too much for funding they can introduce unfortunate biases (that serve the ends of companies...  which isn't necessarily bad, but can be not-ideal in some circumstances).

It recently occurred to me that journalism is a public good that would probably benefit a lot if it was treated as one.  (Assuming that in the country there was adequate and effective funding of public goods -- I'm thinking about an ideal situation here).

At present, there seems to be severe difficulties in obtaining sufficient funding for journalism from market forces.  And there's too much bias introduced by funding through market forces.  One, biases towards content that will bring in money (e.g. clickbait), rather than on quality content.  And two, biases towards what will suit the companies paying the journalists.

In an ideal country, people would appreciate the value that public goods provide to them.  They would appreciate all the benefits that come from research, for example.  And they would be more willing to pay taxes to fund substantial research in the country.  And the government would distribute the research funding in a merit-based (and non-politically motivated) fashion.

Journalism could be treated in the same way.  In the same way that government could fund research in an ideal situation they could fund journalism in a merit-based (and non-politically motivated) fashion.