Quote:
Originally Posted by Brutha  Designing such a system isn't easy and needs some smarts but if you succeed you don't have the problem of writing content anymore and you can extend the guide to other problems without any effort on your part.
That the idea of the web2.0 you don't write your content yourself but find a way to let your users build your content. |
Actually designing such a system isn't hard: I start with a very simple initial version, and iterative rapidly based on feedback. As Paul Graham says in
Six Principles for Making New Things :
Quote:
|
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.
|
That's why I'm asking for help: volunteers who believe in the vision so strongly that they're willing to come up with some guides on paper
before the "web2.0" version is ready.
Why? Because the "web2.0" version needs to be built to help guide-writers write guides in the way that they need to write guides. I could sit down and program a "web2.0" version today, and it would be over-engineered and implement solutions that no one wanted, because I don't know what guide-writers need. If instead I start with guides that people want to write, then I'll be meeting the needs of guide-writers and their users.