Incidentally this is a very valuable instrumental topic for doing well on job interviews, specifically in software areas. The problems are usually a mix of skills, "basic" knowledge and a thinly veiled IQ test questions; the latter type rely on "going meta" at some point of problem solving. If I had a good heuristic for this I think I could pass almost any interview :).
E.g. (classic) how do you delete a node from a linked list if you only have (pointer) to that node, not the previous one?
If I had a good heuristic for this I think I could pass almost any interview :).
Sadly, a lot of interviews are more about "likeability" and people skills than pure critical thinking skills. (I wish it were that easy...)
When do you go meta? When do you stop going meta?
In the video Q and A Eliezer offered some advice about this (the emphasis is mine):
In his discussion post "Are you doing what you should be doing?", Will_Newsome identified what seems to be an important guiding principle of meta-thinking:
(where "time-saving results" can be replaced with "greater marginal utility" to obtain a form that is more generally applicable)
Some questions we could explore:
(I plan to try to compile the insights and advice here into a top-level post discussing the principles of, and heuristics for, effective meta-level thinking)
Edit: Changed minor wording and altered the third question posed.