[SEQ RERUN] Joy in Discovery
post by MinibearRex · 2012-03-05T04:31:25.553Z · LW · GW · Legacy · 4 commentsContents
4 comments
Today's post, Joy in Discovery was originally published on 21 March 2008. A summary (taken from the LW wiki):
It feels incredibly good to discover the answer to a problem that nobody else has answered. And we should enjoy finding answers. But we really shouldn't base our joy on the fact that nobody else has done it before. Even if someone else knows the answer to a puzzle, if you don't know it, it's still a mystery to you. And you should still feel joy when you discover the answer.
Discuss the post here (rather than in the comments to the original post).
This post is part of the Rerunning the Sequences series, where we'll be going through Eliezer Yudkowsky's old posts in order so that people who are interested can (re-)read and discuss them. The previous post was Joy in the Merely Real, and you can use the sequence_reruns tag or rss feed to follow the rest of the series.
Sequence reruns are a community-driven effort. You can participate by re-reading the sequence post, discussing it here, posting the next day's sequence reruns post, or summarizing forthcoming articles on the wiki. Go here for more details, or to have meta discussions about the Rerunning the Sequences series.
4 comments
Comments sorted by top scores.
comment by syzygy · 2012-03-06T00:01:00.428Z · LW(p) · GW(p)
I view intellectual property as the logical conclusion of the "unhealthiness" Eliezer is describing. I laugh when I look at all the ridiculous patents and copyrights that exist, but then I get scared when I remember that someone can use legal force against me for discovering those ideas simply because they discovered them first.
comment by Stabilizer · 2012-03-05T04:54:24.863Z · LW(p) · GW(p)
This may be why several people find academic careers a little oppressive. In order to be successful you have to work on problems which people don't know the answer to rather than one you want to know the answer to. The trick I think (I'm in academia) might be to find a problem which lies in the intersection of these two problem sets.
Replies from: shminux↑ comment by Shmi (shminux) · 2012-03-05T07:00:34.473Z · LW(p) · GW(p)
The trick in academia is to find a low-hanging fruit other people in academia care about. And if they do not care about it yet, to do a good enough sales job to make them care.
Replies from: Stabilizer↑ comment by Stabilizer · 2012-03-05T08:34:42.988Z · LW(p) · GW(p)
Yes. But at a fundamental level you should start caring about it too. This may be easier than it sounds because most fields in academia have very good taste and most problems I come across have very interesting structure.
Another trade-off I've noticed: when do you work on a problem suited to your thinking toolkit and when do you try to figure out the basic skeletons of a problem you are not comfortable with but you would be very interested in once you understand the language and structure of the problem. I'm interested in ways in which I can build my thinking tools to be highly generalizable and broadly applicable, but at the same time powerful enough to be able to use it to attain specific useful results. Any suggestions people?