iWaiter Teachings of "The Cathedral and the Bazaar" (I)
In the previous post
Wednesday, October 15, 2008
Backpacking With A Dslr
commented on "The Cathedral and the Bazaar" , an essay by Eric S.
Raymond
talking about their experiences with Sofgüer
Free and Open Source
and the comparison made between the development models of proprietary and sofgüer sofgüer free.
Among the activities conducted by the author and are collected in the trial, frequently exposed learned from experience during the process. Then I rise to speak to them and comment on them:
if personal ties programmer. ( Every good work begins when you have to scratch your own itch ) In fact that's how all Sofgüer Free Movement began ... Richard Stallman got tired of not being able to modify the programs I needed to change to make them work well and started programming everything from scratch with their friends. 2) Good programmers know what to write. The best, what to rewrite (and reuse). If scheduling is difficult, know to understand the code of another even more so. 3) "Consider disposal, in any case have to." (Fred Brooks, The Mythical Man-Month The idea always is to put bricks on bricks that other people made. No need to invent the warm water. However, sometimes it's easier, more efficient and faster clean slate and do it all again.
4) If and s the right attitude, you will find interesting problems. The trick to a good program is to solve important problems, which have good input anyone has. That's the trick of a successful program.
5) When you lose interest in a program, the last duty is to inherit
a
its competent predecessor. Yes ... discard hurt a child, but if you can not keep, better give it to someone responsible who can.
6) Treating your users as partners is the most appropriate way to improve the code, and debug more effectively.
all unconsciously know that a programmer could try a program so that it does not fail. It is no secret that when a program is used by the public is when the problems start jumping. So why not use this to find mistakes in preliminary versions of the release of a program?
7) Free Ra
often ask, and listen to their customers. What good is a program if no one uses? Listening to users is the easiest way to understand what they need ... (Although now that I think many times I have encountered users who do not know what they want) ... Well, the point is that the earlier versions being released, more feedback can be obtained, and therefore better target the course to be taken the program. The ensayito this experience emerge even more important, but these will be commenting on the next post. Good night.
"Experience is not what happens to you,
but what you do with what happens to you." Aldous Huxley
4) If and s the right attitude, you will find interesting problems. The trick to a good program is to solve important problems, which have good input anyone has. That's the trick of a successful program. 5) When you lose interest in a program, the last duty is to inherit
a
its competent predecessor. Yes ... discard hurt a child, but if you can not keep, better give it to someone responsible who can.
6) Treating your users as partners is the most appropriate way to improve the code, and debug more effectively.
all unconsciously know that a programmer could try a program so that it does not fail. It is no secret that when a program is used by the public is when the problems start jumping. So why not use this to find mistakes in preliminary versions of the release of a program?
7) Free Ra
often ask, and listen to their customers. What good is a program if no one uses? Listening to users is the easiest way to understand what they need ... (Although now that I think many times I have encountered users who do not know what they want) ... Well, the point is that the earlier versions being released, more feedback can be obtained, and therefore better target the course to be taken the program. The ensayito this experience emerge even more important, but these will be commenting on the next post. Good night. "Experience is not what happens to you,
but what you do with what happens to you." Aldous Huxley 
Subscribe to:
Post Comments (Atom)
0 comments:
Post a Comment