DanielLC comments on The Sin of Underconfidence - Less Wrong

55 Post author: Eliezer_Yudkowsky 20 April 2009 06:30AM

You are viewing a comment permalink. View the original post to see all comments and the full post content.

Comments (176)

You are viewing a single comment's thread. Show more comments above.

Comment author: [deleted] 20 April 2009 10:05:41AM 25 points [-]

I wonder if the decline of apprenticeships has made overconfidence and underconfidence more common and more severe.

I'm not a history expert, but it seems to me that a blacksmith's apprentice 700 years ago wouldn't have had to worry about over/underconfidence in his skill. (Gender-neutral pronouns intentionally not used here!) He would have known exactly how skilled he was by comparing himself to his master every day, and his master's skill would have been a known quantity, since his master had been accepted by a guild of mutually recognized masters.

Nowadays, because of several factors, calibrating your judgement of your skill seems to be a lot harder. Our education system is completely different, and regardless of whatever else it does, it doesn't seem to be very good at providing reliable feedback to its students, who properly understand the importance of the feedback and respond accordingly. Our blacksmith's apprentice (let's call him John) knows when he's screwed up - the sword or whatever that he's made breaks, or his master points out how it's flawed. And John knows why this is important - if he doesn't fix the problem, he's not going to be able to earn a living.

Whereas a modern schoolkid (let's call him Jaden) may be absolutely unprepared to deal with math, but he doesn't know exactly how many years he's behind (it's hard enough to get this information in aggregate, and it seems to be rarely provided to the students themselves on an individual basis - no one is told "you are 3 years behind where you ought to be"). And Jaden has absolutely no clue why that matters, since the link between math and his future employment isn't obvious to him, and no one's explaining it to him. (School isn't for learning; as Paul Graham has explained, "Officially the purpose of schools is to teach kids. In fact their primary purpose is to keep kids locked up in one place for a big chunk of the day so adults can get things done. And I have no problem with this: in a specialized industrial society, it would be a disaster to have kids running around loose.")

Another modern schoolkid (let's call her Jaina) may be really skilled at math, but testing won't indicate this strongly enough (it works both ways; tests saturate at the high end - especially if they're targeting a low level of achievement for the rest of the class - and "you are 3 years ahead of everyone else in this room" is not feedback that is commonly given). And there's a good chance it won't be obvious to her how important this is, and how important becoming even more skilled is. And if she ends up being underconfident in her ability, and the feedback loop ("I know how skilled I am, I know why becoming stronger is important, and I know what I need to do") isn't established, then instead of learning plasma physics and working on ITER or DEMO, she goes into marketing or something. Maybe doing worthy things, but not being as awesome as she could have been.

My point, after this wondering, is that I agree with this post, and want to elaborate: structuring what you do so that you test yourself in the process of doing it is a good way to establish a feedback loop that increases your skill and the accuracy of your confidence in it. I find nothing wrong with the debating example in this post, but I worry that it makes self-testing sound like something that you should go out and do, separate from your everyday work. (Part of this, I think, is due to Eliezer's very unusual occupation.) My usual self-testing example is something like "can I write this program correctly on the very first try?". That's a hard challenge, integrated into my everyday work. Successfully completing it, or coming close, has allowed me to build up my skill ("the compiler in my head") and avoid the danger of underconfidence.

Comment author: DanielLC 08 May 2013 06:02:08AM 0 points [-]

My usual self-testing example is something like "can I write this program correctly on the very first try?".

I never thought of that as a thing you could do. I think when my code compiles on the first try, it's more often then not a sign of something very wrong. For example, the last time it happened was because I forgot to add the file I was working on to the makefile.

Perhaps I should try to learn to code more precisely.

Comment author: [deleted] 08 May 2013 06:36:13AM 0 points [-]

Heh. (You should use makefiles that automatically build new files, and automatically sense dependencies for rebuild.)

As I recall, Eliezer said somewhere that I'm too tired to Google - there is no limit to the amount of intelligence that you can use while programming.