Web2.0 Programming Idea: 16 rule _web2.0

1, before you start, set a simple goal. Whether you're the creator or user of a Web 2.0 application, be clear about your goals. It's like "I need to save a bookmark" or "I'm ready to help people create editable, shared pages" so that you can maintain the most basic needs. The initial attraction of many Web 2.0 applications is its simplicity, avoiding and hiding the extra complexity. Standing in the founder's position, you can imagine Google's home page with almost no content, as well as del.icio.us simple lines. From the end user's point of view, it is the same as the diggdot.us provided by the initialization of the page. You can and want to add more features, but do the first thing. Do one feature at a time and accomplish a goal. It sounds too simplistic, but it will make you more focused and you will understand what I mean.

2, link is the most basic idea. This is one of the reasons we call the Web. A link is the most basic element that connects the various entities in the Web. Your information, your relationship, your navigation, and even any content that can be written as a URL. Here is a link to follow the rules (in fact you do not have to strictly adhere to):

1. Everything on the Web can be connected by a URI or a URL.

2. Save all links as his original source, so that you can share it with anyone, anywhere, and anytime.

3. The premise at any time in the second article is that the link must be persistent and it will not be changed or disappear without any cause.

4. Links should be human-readable, stable, and able to interpret themselves.

3. The data should belong to the person who created it. Yes, you listen to me. Any user created, contributed, or shared is their own, unless they clearly give up this power to allow you to dispose freely. Any information they contribute to the web should be editable, deleted, and able to be unshared, at all times, as long as the user is willing. It also contains indirect data, such as records, logs, browsing history, site access information, or any information that can be tracked. All Web sites must be clear and simple to make a statement that the information is created by the user and provides methods that they stop creating, or even methods of elimination.

4, data first, experience and function second. No 鬯  Qiao seek to do ⑼ meter ⒁ 羝 prayer so sheath leisurely 琖 EB finally put these resolution as data. In other words, you cannot render content out of the data. All of this data is located through URLs that are easy to discover (see 2nd). Looking at these in another form, the web is ultimately a noun priority, followed by a verb, although it is recently being shifted to a verb. Take a look at examples of nouns: calendar entries, family photos, stock prices. There are also some examples of verbs: make a date, share a picture, buy a share.

5, do a good job of sharing all the preparation. Share as much as you can, all the data you have, all the services you provide. Encourage not to follow the original intent of the use, advocate contributions, do not want to share the content of the insistence set to private. After sharing and discovering, providing an easy-to-use way of browsing is an obvious requirement. Why: In other words, you will benefit from the sharing of others. Note: There is no license to violate copyright laws, you cannot share your DVD or have commercial copyright music because you have agreed not to share it. But you can find and share those completely open media content. A little advice, you can learn about creative Commons License (co-creation Agreement).

6, the web is a platform, to let it grow. Of course, we have a lot of other platforms (Windows, Linux, Mac), but that's not the point anymore. In other words, the web is a platform that cannot be detached, a platform that will not be interrupted, and you can extend the platform in various ways. The data and services you provide on the web will become part of the web, and eventually you will play your part on the web platform somewhere. Play your part and take good care of the latter.

7, understand and believe in "ladder sex". Now the web is growing, spreading almost all over the world, and already has 1 billion users. My point is that there are nuances and differences in the various components of the Web, just like users in different places. For example, the design part of the Web: Ease of use always takes precedence over speed, reliability, reusability, and scalability. You should also provide the same experience to your users. It has been stressed again and again by people in the document, loyal users will soon become professional users, they expect faster speed and more. Step back and support them. Also, there are a lot of users who will enter the bottom of the ladder, as you would expect. They may not speak your language, are unfamiliar with your culture, and don't even know how to get here. So you need to show them clearly.

8, everything is editable. Or it should be woven better. To be sure, only a few things can not be edited, the rest are OK, this is a writable web. This does not mean that the original content is lost, but it is often understood that the user can easily comment on the content, or the commentary is found there. If you apply it well, they can do more than you think (string up content and give the original content to create your own, etc.).

9, the identity on the web is sacred. Unfortunately, this does not mean that you can get more privacy (this is entirely the idea of the last century). But verification of identity is necessary, and you should be thankful for services that can determine your identity with just one email address. This means that as long as you promise to your users, you have to keep their privacy safe. When necessary, somewhere in the world you have to stand up for your users and challenge local authority. If you don't plan to do that, you'll have to tell your users the truth. On the other hand, if identity is necessary, don't try to disguise it, otherwise we will give up our last little privacy right on the Web one day.

10, understand the popular standards and use them. From the standpoint of a consumer or creator, data will be exchanged in different formats with anyone. At the same time, such data will in turn promote the improvement and adoption of standards. This usually means the popularity of simple criteria like RSS, OPML, XHTML, plain XML, JSON, and avoiding soap, XSD, and RDF and Atom, and using them will bring pain to my heart. Please also vote for your favorite criteria to support them.

11, follow the law of unintentional use. If you open and share very interesting data and services in a widely used format, you will get what you deserve and others will build on your web platform. Maybe you'll get more from others, so it's better to prepare for this. I can't remember how many times I saw a podcast (podcasting) service collapse because of a popular transition because they were included by Slashdot and del.icio.us. It's important to know that the mass on the web means that if a content is very interesting, even a small corner will get an amazing amount of traffic. Encourage the use of this method, it is still very valuable, if you want to be prepared.

12, granular your data and services. We should have known this a long time ago, the data of large-scale integration is only suitable for download and bulk operation without management. Break down your data and make them independent of the URL address you are describing, as well as your service. Conversely, you should not create huge, complex, tree-like data structures and services. Keep it simple, it's very simple. Let these pieces of separation be easily reorganized and discovered.

13. Provide data and services that users can benefit individually. It's risky to rely on this kind of socialization, and you need to give your users a little incentive to contribute time, enthusiasm and information unless they can benefit directly. Social sharing is much more beneficial than individual behavior, unless you can motivate the user's personal motivation, and you will not be able to enjoy the gift.

14, let users organize and filter information. It is not necessarily necessary, but it is very important. Let users label and organize data in their own way, because you will never be able to deal with them in time. Users are treated and built in the best way they can understand them. Make sure that your Web services work the way users want them to be. This is also the main factor in the way that labels (tagging) and popular classifications (folksonomies) are so successful.

15, provide a rich user experience. The web has been fiercely competitive with local applications. Why? Because the local program still feels better and faster. But it's not going to last long (make sure that the competition doesn't exist in 5 or 15 years). Yes, I'm talking about rich Internet applications, Ajax, and incredibly interactive apps. They make the web a real "platform-free" platform, if you know what I think.

16, believe in and support rapid improvement and feedback. This usually means speeding up the pace, but it also means using lightweight tools, techniques, and not making those counterproductive decisions (such as using a layered AJAX framework instead of the one that can be implemented by mixing, or building everything in C + +, in fact, it's better to use Ruby). This also means that you need a very fast way to handle error reporting, fix bugs, and release new versions. From a user's point of view, report any problems you find, and where you often complain, even if they are not a bug.
Of course, Web 2.0 is an extremely broad and esoteric topic, and no one can enumerate all its priorities and characteristics. If you are interested in this, please take a moment to supplement what I have not mentioned. I think this is the participation of Web 2.0!

The original author's title draws on Bruce Eckel's two best-selling books: "Thinking in C + +" and "Thinking in Java", "C + + programming Ideas" and "Java programming ideas", which explains why this topic is translated in this way: