What can enterprise developers learn from Web 2.0?

Author: builderau.com. au AM

With the recent arrival of Web 2.0, people are paying close attention to it and discuss it in various aspects. However, it has not been thoroughly discussed yet: compared with other traditional enterprise software development, what unique development methods does Web 2.0 have? In this topic, Stephen Bryant recently published the five most representative reasons why Web 2.0 cannot be mixed with elasticsearch. Stephen's point of view focuses on the various problems that many large companies encounter when using Web 2.0. ArticleStephen expressed his rejection of "top-down innovation. However, I would like to point out that this idea will cause many companies to reject the use of Web 2.0 and decentralization of various blogs, wikis, and even mash-up. When software development with a Guiding Direction (pull-oriented) such as Web 2.0 appears, it will be "in conflict" with the enterprise software development system, which is a typical cultural conflict. Interestingly, McKinsey's latest report states that the vast majority of innovations in the future will come from systems in various forms of guidance, and "when such systems are at the center, the executive will review all aspects of the company." Well-blogged of the tie incident also raised many points this month. Among them, the most representative is that the idea of Web 2.0 will lead to innovative business operation models beyond the technical level. It is also suggested that traditional enterprises should learn to give up control of certain data access when developing software. The rapidly developing Web 2.0 is essentially different from the cumbersome processing process of enterprise software. Popular agile software processes, including scrum and lean software development, have worked hard to overcome disadvantages such as bloated traditional software development and complex central control. The old design process usually involves redundant and cumbersomeProgramThese sections impede the company's development efficiency. Therefore, agile proposed a set of development theories, claiming that feedback loops and descriptive languages are quite useful for software release. Over the past few days, rapid development and popular agile software development have been deeply rooted in the hearts of the people. The famous Agile Manifesto clarifies the following points to illustrate the core of their design philosophy (we can see that it is very similar to the concept of Web 2.0 ): AgileMethod Core Based on the process and the mutual independence and interaction between tools; Software Based on comprehensive documents; User cooperation based on contract negotiation; All planning-based decisions. Now, let's look at the development ideas related to the establishment of Web 2.0 software. Web 2.0Development Ideas Regular release: a product is released every 30 minutes (for thousands of users ). Benefits: errors can be reduced as soon as possible, and the software development process will become a continuous and smooth process. Small program segments and loose connections: Make updates easier and have fewer risks. Similarly, each part has better reusability and sharing. Lightweight program model: Dynamic Language: such as rub and simple data format, such as Really Simple Syndication (RSS) and representional state transfer (rest) can make program development, integration, testing and reusability easier and more efficient. Users can act as creators: users can participate in the Web 2.0 center. Provide users with dynamic features they need, and provide them with information that supports online software. Real-time feedback and information extraction: by observing the user's current use and feedback methods, users need to know the features and functions to build a perfect product step by step. You can also note that Web 2.0 has listed many rules for software development, including: Spend less money: Encourage the maximum use of resources, and the minimum investment. Less manpower: make the least effort in human resources and focus on product development. More specific: Reduce Unnecessary design links. Question: How can these rules be applied to traditional enterprise software development? Web 2.0 software development includes some small startup programs. I have heard and seen that none of these startup programs are well translated into traditional enterprise software. Isn't Web 2.0 software "translating? The simple answer is that there is still a "gap" between the two ". On the one hand, our small software developers use some extreme development methods. However, these methods lack resources and developers have to satisfy the requirements of current and potential users through quick feedback. On the other hand, we usually invest a lot of money and detailed project plans in large-scale software development, but the benefits are very slow.   Although agile/lean continues to develop in enterprise development, compared with Web 2.0, the agile/lean method is a little cumbersome. I don't want to answer how Web 2.0 development technology is transformed into traditional enterprise development. However, we have seen that the agile method has been applied to more and more projects in recent years. Some agile experts, such as Jutta Eckstein, believe that the agile method can be effectively applied to project development with up to 200 people. This gives the current innovative, fast feedback, and low-cost web development technology the ultimate hope for enterprise development. If you read Marc Hedlund's excellent report, you will find that these new technologies will develop rapidly. This article has come to an end. I will track this technology and provide more information in the future.