There has long been in the field of software development methodologies for a lot of talk and
discuss what the process more efficient or better suited In ... ' field of web technologies (which are now the leading technologies for all software farm, or at least those on which there is greater expectation) now has in fact said the concept of perpetual beta (Perennial beta) ... software that is evolving so fast and so attached to business not adequate to reach a stable version of the product. The paradox is that the online version of the software web, although still in beta, has a level of inherent stability also given the ability and habit of mind of the developer that evolve and keep it in operation to update progressively and fixare bugs and new features continuously ... They synchronize and stabilize the software almost every day ...
In fact, and few point out, this method of practice now in web (see Google and its consolidated philosophy always in beta version) has a precursor in the workplace and in theory made by Microsoft since the first versions of Windows (years 80) by a process known as Synchronize-and-Stabilize .
Synchronize-and-Stabilize the software development process is a very effective and mainly directed towards the realization of the product ... as the Americans say so heavily focused solely to ship products.
Here are the words that describe effectively the philosophy development software, Chris Peters, l’Architetto Microsoft che guidò il team che integrò, in modalità Synchronize-and-Stabilize, le prime versioni di Microsoft Office :
“ Everybody in a business unit has exactly the same job description and that is to ship products. Your job is not to write code. Your job is not to test. Your job is not to write specs .
Here are the words that describe effectively the philosophy development software, Chris Peters, l’Architetto Microsoft che guidò il team che integrò, in modalità Synchronize-and-Stabilize, le prime versioni di Microsoft Office :
“ Everybody in a business unit has exactly the same job description and that is to ship products. Your job is not to write code. Your job is not to test. Your job is not to write specs .
Your job is only to ship products ....
When you wake up in the morning and you come to work, you say what is the focus? Are we trying to ship? Are we trying to write code? The answer is we are trying to ship.... You're trying not to write code.
If We Could make all this money by not writing code, We'd do it. "
0 comments:
Post a Comment