Ci sono paradigmi that change, and do not realize it. Who has a minimum followed the evolution of software engineering was clear that the software is a product life cycle. There is the invention, there is development, then there's the testing. Testing is fascinating. It begins with the pre-alpha, where the features are not complete and a few close friends start to try, doing a slalom between failures and bugs, hopeful. The guru of the few pre-alpha, people who usually would be able to do a calculation to a toaster also able to enter data in binary, are integrated with others, not programmers sleepers, people who spend their nights to try and install, usually malnourished and without social relations, happy to test and have the latest, whatever that is. One day the product matures, and goes to Beta, a version that can be spread to humans, to all who want it, where the probability of failure is located at an acceptable threshold, but unknown. All are quick to have the beta, because the news is always a sign of distinction, because there are ads feature and useful and never had, because maybe there will be no money to take the final version and then at least you have the thrill of have been the object itself. After the beta changes depending on the evolution of the parent, however you can get the product or release candidate, which would be the final product that can be tried without being purchased, and while we're at, do some additional testing.
Well, that no longer exists. Today we have Web 2.0, applications running inside the browser, so the idea is that we take them in beta, we use the world as a tester, and leave them in beta forever. An example, among all, is gmail. In beta since 2004, after five years it still is and probably will remain so forever, but this does not matter. The idea is that the product is evolving. Being accessible from the web, the "code" that is the object that governs the functionality, it is downloaded every time we connect. It can then be updated every day, even more times a day. The features are introduced gradually, the product evolves, and you almost do not you know it. Every now and see a new button. Every so often you have a new function. Every so often you have a new look and feel available, but all is well compatible with the previous day and almost did not you know it. The so-called corrective maintenance (for errors) and evolutionary (for new features) is completely embedded in the continuous new changes, we can no longer call release, not only because I have no indication of what release I'm using, but I probably will change between few hours and above is different from OS to OS, but also between the browser and browser.
Evolving, leading to beta write next to the name of the product, beta once meant object in debug probably full of errors that distrust, now it 'dynamic object that is constantly changing and that is the result of a worldwide collaboration and continuous of a constant evolution, with no plans known but the results were appreciated. It 's a different world. Realize it really hard. Furthermore, a new specter is haunting in the web 2.0 and beta. It is called caching. If it is true that my whole life is organized by some software, it is true that social relations are also my oversaw these systems, it is assumed that the mode of operation is web 2.0, web 2.0 if it works in a browser connected to the network, what ever happens to me if they are disconnected? Even for a few seconds, but in a second key. Suddenly I no longer have access, I do not have a piece of myself. So caching. The browser becomes smarter and syncs with the Internet, data and programs Allien equally appreciated by the browser between the network and the local browser. I know if I stop or not access, I cease to know when they are connected and when not. We think of him in a ballet between realtime and caching, always and automatically synchronized. All this, of course, always and only in beta.
Long live the beta, beta forever.
Well, that no longer exists. Today we have Web 2.0, applications running inside the browser, so the idea is that we take them in beta, we use the world as a tester, and leave them in beta forever. An example, among all, is gmail. In beta since 2004, after five years it still is and probably will remain so forever, but this does not matter. The idea is that the product is evolving. Being accessible from the web, the "code" that is the object that governs the functionality, it is downloaded every time we connect. It can then be updated every day, even more times a day. The features are introduced gradually, the product evolves, and you almost do not you know it. Every now and see a new button. Every so often you have a new function. Every so often you have a new look and feel available, but all is well compatible with the previous day and almost did not you know it. The so-called corrective maintenance (for errors) and evolutionary (for new features) is completely embedded in the continuous new changes, we can no longer call release, not only because I have no indication of what release I'm using, but I probably will change between few hours and above is different from OS to OS, but also between the browser and browser.
Evolving, leading to beta write next to the name of the product, beta once meant object in debug probably full of errors that distrust, now it 'dynamic object that is constantly changing and that is the result of a worldwide collaboration and continuous of a constant evolution, with no plans known but the results were appreciated. It 's a different world. Realize it really hard. Furthermore, a new specter is haunting in the web 2.0 and beta. It is called caching. If it is true that my whole life is organized by some software, it is true that social relations are also my oversaw these systems, it is assumed that the mode of operation is web 2.0, web 2.0 if it works in a browser connected to the network, what ever happens to me if they are disconnected? Even for a few seconds, but in a second key. Suddenly I no longer have access, I do not have a piece of myself. So caching. The browser becomes smarter and syncs with the Internet, data and programs Allien equally appreciated by the browser between the network and the local browser. I know if I stop or not access, I cease to know when they are connected and when not. We think of him in a ballet between realtime and caching, always and automatically synchronized. All this, of course, always and only in beta.
Long live the beta, beta forever.
0 comments:
Post a Comment