44 lines
3.4 KiB
Markdown
44 lines
3.4 KiB
Markdown
|
---
|
||
|
|
title: 'Paul Graham: Six Principles for Making New Things'
|
||
|
|
author: kazu634
|
||
|
|
date: 2008-02-25
|
||
|
|
url: /2008/02/25/paul-graham-six-principles-for-making-new-things/
|
||
|
|
wordtwit_post_info:
|
||
|
|
- 'O:8:"stdClass":13:{s:6:"manual";b:0;s:11:"tweet_times";i:1;s:5:"delay";i:0;s:7:"enabled";i:1;s:10:"separation";s:2:"60";s:7:"version";s:3:"3.7";s:14:"tweet_template";b:0;s:6:"status";i:2;s:6:"result";a:0:{}s:13:"tweet_counter";i:2;s:13:"tweet_log_ids";a:1:{i:0;i:3767;}s:9:"hash_tags";a:0:{}s:8:"accounts";a:1:{i:0;s:7:"kazu634";}}'
|
||
|
|
categories:
|
||
|
|
- diary
|
||
|
|
- Paul Graham
|
||
|
|
- メモ
|
||
|
|
|
||
|
|
---
|
||
|
|
<div class="section">
|
||
|
|
<p>
|
||
|
|
こいつは面白いです(→<a href="http://www.paulgraham.com/newthings.html" onclick="__gaTracker('send', 'event', 'outbound-article', 'http://www.paulgraham.com/newthings.html', '原文');" target="_blank">原文</a>・<a href="http://d.hatena.ne.jp/lionfan/20080224#1203759642" onclick="__gaTracker('send', 'event', 'outbound-article', 'http://d.hatena.ne.jp/lionfan/20080224#1203759642', 'id:lionfanさんの翻訳');" target="_blank">id:lionfanさんの翻訳</a>）。
|
||
|
|
</p>
|
||
|
|
|
||
|
|
<p>
|
||
|
|
気になる部分はやっぱり
|
||
|
|
</p>
|
||
|
|
|
||
|
|
<blockquote title="Six Principles for Making New Things" cite="http://www.paulgraham.com/newthings.html">
|
||
|
|
<p>
|
||
|
|
Here it is: I like to find (a) simple solutions (b) to overlooked problems (c) that actually need to be solved, and (d) deliver them as informally as possible, (e) starting with a very crude version 1, then (f) iterating rapidly.
|
||
|
|
</p>
|
||
|
|
|
||
|
|
<p>
|
||
|
|
When I first laid out these principles explicitly, I noticed something striking: this is practically a recipe for generating a contemptuous initial reaction. Though simple solutions are better, they don’t seem as impressive as complex ones. Overlooked problems are by definition problems that most people think don’t matter. Delivering solutions in an informal way means that instead of judging something by the way it’s presented, people have to actually understand it, which is more work. And starting with a crude version 1 means your initial effort is always small and incomplete.
|
||
|
|
</p>
|
||
|
|
|
||
|
|
<p>
|
||
|
|
I’d noticed, of course, that people never seemed to grasp new ideas at first. I thought it was just because most people were stupid. Now I see there’s more to it than that. Like a contrarian investment fund, someone following this strategy will almost always be doing things that seem wrong to the average person.
|
||
|
|
</p>
|
||
|
|
|
||
|
|
<p>
|
||
|
|
As with contrarian investment strategies, that’s exactly the point. This technique is successful (in the long term) because it gives you all the advantages other people forgo by trying to seem legit. If you work on overlooked problems, you’re more likely to discover new things, because you have less competition. If you deliver solutions informally, you (a) save all the effort you would have had to expend to make them look impressive, and (b) avoid the danger of fooling yourself as well as your audience. And if you release a crude version 1 then iterate, your solution can benefit from the imagination of nature, which, as Feynman pointed out, is more powerful than your own.
|
||
|
|
</p>
|
||
|
|
|
||
|
|
<p>
|
||
|
|
<cite><a href="http://www.paulgraham.com/newthings.html" onclick="__gaTracker('send', 'event', 'outbound-article', 'http://www.paulgraham.com/newthings.html', 'Six Principles for Making New Things');" target="_blank">Six Principles for Making New Things</a></cite>
|
||
|
|
</p>
|
||
|
|
</blockquote>
|
||
|
|
</div>
|