Before asking for help, they made a wrong decision, which maybe solved their short term problems but shot them in the foot in the long term. This bad decision made other bad decisions more likely until they were helplessly stuck in a trap of their own making.
It's worth noting that there are domains where there are no experts. In those domains people who explore them still tie themselves up.
A class of people who thinks of themselves as experts but doesn't really have a clue is the most dangerous when it comes to trapping themselves in traps of their own making.
AGI development is the obvious example for LessWrong and other examples are better left as exercise to the reader.
It's worth noting that there are domains where there are no experts
If I were to write a follow-up talking more about this expert-novice divide, I'd focus on defining expert/novice not based on their absolute level of knowledge/experience in the field, but relative to some specific person. E.g. someone might be an expert in AI safety compared to their grandma, but a novice in AIS compared to Yudkowski.
I think defining experts/novices as relative labels is more informative than saying there are domains where there are no experts. I agree that there are domains where everyone has barely an elementary understanding of the field, but within that narrow range of expertise I think it's still useful to have a term for those at the upper end of the range compared to those at the lower end (although this is mostly semantics).
A class of people who thinks of themselves as experts but doesn't really have a clue is the most dangerous when it comes to trapping themselves in traps of their own making.
I wouldn't define these people as experts. 100% agree that they're the most dangerous, especially if they've learnt to disguise themselves as experts without actually having the required expertise. In the essay I mostly ignored people who are dishonest and try to disguise themselves as experts/novices when they're not. Maybe that's a post for another time.
On second reading, you might be referring to people who honestly believe themselves to be experts but actually have no clue what's going on? That's something I didn't consider. Again I agree that they're dangerous. It feels like the sort of thing LessWrong would have written about before? I'm curious about how one could discover that you're in this category of honestly-but-fake experts.
If you go to Yudkowski and say "Hey, I want to build an AGI, can you please tell me how to do so safely?", he will answer "I can't tell you how to build an AGI safely. If you are going to successfully build an AGI you are likely to kill us all. Don't build an AGI".
Yudkoswky is self-aware that he doesn't have the expertise that would be necessary to build a safe AGI. If you then search for an expert who gives you some advice about how to build your AGI and you succeed in building your AGI and kill everyone, that was a trap of your own making.
If you want a past example, David Chapman´s article about Domestic Science is great. More recently, you had a flatlining of childhood obesity rates in the second Bush administration. Afterwards, Michelle Obama started a huge program to improve childhood nutrition through various measures recommended by nutrition scientists. After those programs childhood obesity rates were rising again.
Scientists studying nutrition do believe themselves to be experts, but seem to give advice that produces more problems than it solves.
Reality doesn´t just reward you for having put in a lot of effort.
Something that's painfully understudied is how experts are more efficient than novices while achieving better results. I say understudied and not unstudied, because it's common knowledge that charging people for their time results in experts being paid less since they work faster, which is why experts charge more for their time.
This effect is understudied in the impact it has on novices entering a field. A Novice will start out being woefully inefficient, putting in incredible amounts of effort and running through all number of mental hoops in order to maintain
the growing pile of unmaintainable abstractions they've developed. An expert doesn't have to jump through these hoops. They can more clearly see the actual problem at hand and will more efficiently put their time and effort towards
making progress against the problem. In contrast, novices will spend more time battling problems they created for themselves. Let's explore this idea by looking at two characters entrapped in a maze, and how they go about escaping.
Stuck in a maze: Expert vs Novice
Some of the trickiest tangles I've tackled haven't been because the core problem is difficult, but rather because I was helping someone with less experience, and they spent several hours getting themselves more and more tied up. Before asking for help, they made a wrong decision, which maybe solved their short term problems but shot them in the foot in the long term. This bad decision made other bad decisions more likely until they were helplessly stuck in a trap of their own making.
Often this trap is far trickier than anything an expert would let themselves get into. Novices, on the other hand, can easily make a sequence of bad decisions that result in an ever increasing cost of solving the problem at hand. Not only are you lost in the maze without your twine, but you also went in a mysterious cave that looked kinda interesting at first and now you're lost in the dark. Meanwhile, the world-class expert is happily skipping through the warm sunny parts of the maze, because they knew that the cave would eventually lead to a dead end.
I'd like to stress at this point that this is in no way the Novice's fault. They followed the same policy as any expert: "take best action available to you at the time". Telling a Novice to "just be better" is not constructive feedback. This feedback does not lead to them improving over time, since from the only perspective that matters in this scenario (the Novice's), they were taking the best action available to them. And if you're giving feedback that doesn't lead to improvement, what's the point of the feedback?
The Novice has a genius idea
Novices often spend energy fixing things that are orthogonal to the actual problem they want to solve, whereas experts are able to better direct their energy towards the problems they want to solve. This leads to novices having an extremely distorted view of a field, because the problems they end up solving are both more difficult and less interesting than those being tackled by experts. Nobody wants to put more effort into figuring out a more boring problem.
The Novice's search strategy
For a Novice, the vast majority of decisions have to be made essentially randomly, with very little information going into the choice. If all decisions were sequential and did not depend on any other decision, a dedicated Novice could come up with a solution better than random chance after thinking hard about the decision. But the world we live in is fractal and complexly dependant; many decisions depend on other decisions in ways that a Novice has no idea about. Even a dedicated Novice will be confronted with situations in which they must make several inter-dependant decisions before they can get feedback on the efficacy of those decisions. The Novice is (at first) forced to make completely arbitrary choices and face the consequences. Hopefully they can learn which consequences were due to which decisions, but this isn't always feasible.
From the perspective of an expert, the decisions taken while solving a problem are often second nature, and yet are carefully crafted so as to avoid unnecessary trouble down the road. A Novice looking upon an expert's work would be hard-pressed to distinguish these few important decisions (based on years of hard work and study) from the myriad of far less important decisions (based largely on personal taste).
Novices don't even see the decision
Sometimes the Novice doesn't even know that there's a decision to make. When the decision is pointed out by the friendly expert, the Novice can often either make the correct decision or appreciate the correct solution when it's shown to them. But the Novice _didn't even know there was a decision in the first place_. This makes it incredibly difficult for the ambitious Novice to make progress without outside help. They cannot just "check their work for mistakes", because for any substantial body of work the Novice likely wouldn't be able to point out half their decisions.
Experts can't explain their decisions
The expert's intuition is often formidable, but rarely comprehensible. This inability to clearly explain their decisions is what makes it so useful for novices to spend time with experts. Often there's an underlying pattern that the novice can pick up through careful observation, even if neither the expert nor the novice can properly articulate this pattern.
The Expert's ensemble
Experts often have either a network of people, or (more frequently nowadays) know the online network of websites and usernames which can guide their thoughts. They can quickly distinguish useful insight from helplessly generic summaries, and don't have to spend much time looking for the information they're after. But a Novice has _no clue_ about how to distinguish the two, nor how to find communities who can help them effectively.
Escape
As a Novice, you _need_ to find a sympathetic expert on your side to help you out and to whom you can ask all questions, regardless of how trivial the questions might be. A replacement for this is finding a lot of experts so you can spread the load amongst them. You can go very far online nowadays, and even more so with AI tools. But many of the above trappings that novice's succumb to do not magically disintegrate because you have access to the internet or to a chatbot. You still don't know how to recognise subtle decisions. You still don't know how to distinguish good ideas from bad. You still don't know how to avoid long-term cascades due to bad choices. The internet helps, for sure, but having someone by your side is monumentally better.
One thing that can be tricky to convey to your friendly expert, is that sometimes you just need to be able to show them what you're doing without any specific question in mind. I've often found that I can feel uneasy about what I'm doing, and then talking with an expert friend will quickly surface that I've made some error that will cause pain later. Having someone who's happy to spend time "just talking", without any specific goal to solve, will go a long way.
In the workplace, this style of "just talking" interactions between novices and experts is critical for knowledge transfer and training. But novices rarely have a voice with key decision makers, and so promoting these interactions is often neglected. It is not sufficient to instruct senior employees to answer the newcomer's questions, since the vast majority of learning comes from a novice watching how the expert plies their skills, and not from direction questions and answers. What makes this scenario even trickier is that the expert will likely think "just talking" interactions are basically worthless, but answering concrete questions _feel_ much more useful. The novice, on the other hand, could likely discover answers to concrete questions on their own, given enough time. But developing the intuitions that come through while an expert is "just talking" with a novice is incredibly valuable to the novice. This explains the difficulty of training new employees when all your experts are working remotely, as remote work practically eliminates any sort of casual unguided "water-cooler" interaction.
Something you can do independently (and possibly it's best done without expert supervision), is exploration of the field. You know nothing, and have no biases about what may or may not be useful. _Any_ time you come across something that feels like it has some depth to it, such as a well-written essay series or a deep technical dive, you need to invest heavily into it. As a novice, your one advantage is that _everything_ is new and nobody expects you to be fast. Because of this, you can afford to spend the time to learn as much as possible.
I honestly don't think it's possible to overdo this. Spending a week exploring some specific arcana of your field is probably going to pay dividends, because all of a sudden you're expert-level in this (_tiny_) aspect of the field. You can go head-to-head with an expert, since they last read about that weird subdomain 5 years ago. Don't study the "common" things, but go all-in on the niche pockets. The common things are common enough that you'll learn them through osmosis regardless of what your main activity is. But the niche things require active study, and ignoring the niches is how you remain a novice.
Amongst all of this, the novice needs courage (to make decisions without knowing the consequences) and confidence (so that they whole-heartedly commit to their decisions and grant them the greatest chance of success). These traits are not trivial, and confidence can easily be crushed by a snide comment from an expert. I don't want to imagine how many promising novices have been spurned by unimpressive experts. In this way, advice from a sour-hearted expert is worse than no expert advice at all due to the risk of destroying the novice's confidence.
Closing thoughts
The lack of consistent empathy between experts and novices would suggest that, despite feeling easy, it is in fact difficult.
In the extreme case, this lack of empathy leads to experts deriding the work of novices as not having the prestige/class/taste/status expressed so deftly by the work of the experts.
This is self-fulfilling: novices will either conform to the expert's sense of aesthetics, dismiss the field of study as "not for them", or (in rare cases) work incredibly hard to prove the experts wrong after all. In this last case, the Novice becomes an expert anyway. Experts tend to have an aesthetic preference towards technically challenging work rather than
simple-but-interesting work.
Originally posted on my blog. Thanks to Daniël Goosen, Paul Hoft von Hoesslin, Dr Lisa Kane, and Tegan Green, and the AI Safety Cape Town writing group chat for reviewing drafts of this essay.