Here's a summary of all the lessons learnt (acc to the author himself) in his seminal "The Cathedral and the Bazaar".
1. Every good work of software starts by scratching a developer's personal itch.
2. Good programmers know what to write. Great ones know what to rewrite (and reuse).
3. ``Plan to throw one away; you will, anyhow.''
4. If you have the right attitude, interesting problems will find you.
5. When you lose interest in a program, your last duty to it is to hand it off to a competent successor.
6. Treating your users as co-developers is your least-hassle route to rapid code improvement and effective debugging.
7. Release early. Release often. And listen to your customers.
8. Given a large enough beta-tester and co-developer base, almost every problem will be characterized quickly and the fix obvious to someone
9. Smart data structures and dumb code works a lot better than the other way around.
10. If you treat your beta-testers as if they're your most valuable resource, they will respond by becoming your most valuable resource
11. The next best thing to having good ideas is recognizing good ideas from your users. Sometimes the latter is better.
12. Often, the most striking and innovative solutions come from realizing that your concept of the problem was wrong
13. ``Perfection (in design) is achieved not when there is nothing more to add, but rather when there is nothing more to take away.''
14. Any tool should be useful in the expected way, but a truly great tool lends itself to uses you never expected.
15. When writing gateway software of any kind, take pains to disturb the data stream as little as possible—and never throw away information unless the recipient forces you to!
16. When your language is nowhere near Turing-complete, syntactic sugar can be your friend.
17. A security system is only as secure as its secret. Beware of pseudo-secrets.
18. To solve an interesting problem, start by finding a problem that is interesting to you.
19. Provided the development coordinator has a communications medium at least as good as the Internet, and knows how to lead without coercion, many heads are inevitably better than one.
I am Ani (and Ashi is my better half) and this is my (our) small e-world. Here's where we will explore our world of joy and sorrow, whims and fancies....experiences (the good , the bad and the not-so-ugly) office-stuff and travelogues...basically a diary of our heart and mind..and what we ramble...
Showing posts with label Open Source. Show all posts
Showing posts with label Open Source. Show all posts
Saturday, May 9, 2009
Friday, May 8, 2009
A Primer to Open Source SW Development Ideas..
A nice modern Zen poem to start the blog:
To follow the path:
look to the master,
follow the master,
walk with the master,
see through the master,
become the master.
Have been doing some study on the Open Source Initiative.
For those who want to have a primer (and it's a lovely read too), here's the most revered article on the subject. It's titles "The Cathedral And The Bazaar" and is written by Eric Raymond.
Coming from Unix background, he was taken in surprise in 1991 by the Open Source movement and became a beliver himself by 1996. He has actually drawn heavily from the experiences he had with Linus Torvalds or Richard Stallman and these have heavily influenced his writings.
Eric is the person who popularised the line "Given Enough Eyeballs, All Bugs Are Shallow". It's actually a one line summary of the concept of a Bazaar (which is how Linux was developed)...where there is no given protocol and ANYONE can say (contribute) whereas the Cathedral mode of development is when there is a Open Source development thru guidelines and frameworks.
Also interesting to note, when you read the article you will start seeing the myriad ways in which Open Source Development is so similar to Agile SW Development Practices.
I found the following ideas of open source development very similar to that of Agile Development.
4. If you have the right attitude, interesting problems will find you.
5. When you lose interest in a program, your last duty to it is to hand it off to a competent successor.
6. Treating your users as co-developers is your least-hassle route to rapid code improvement and effective debugging.
7. Release early. Release often. And listen to your customers
8. Given a large enough beta-tester and co-developer base, almost every problem will be characterized quickly and the fix obvious to someone
10. If you treat your beta-testers as if they're your most valuable resource, they will respond by becoming your most valuable resource.
11. The next best thing to having good ideas is recognizing good ideas from your users. Sometimes the latter is better.
13. ``Perfection (in design) is achieved not when there is nothing more to add, but rather when there is nothing more to take away.''
18. To solve an interesting problem, start by finding a problem that is interesting to you
19: Provided the development coordinator has a medium at least as good as the Internet, and knows how to lead without coercion, many heads are inevitably better than one
So much for today...see you soon
To follow the path:
look to the master,
follow the master,
walk with the master,
see through the master,
become the master.
Have been doing some study on the Open Source Initiative.
For those who want to have a primer (and it's a lovely read too), here's the most revered article on the subject. It's titles "The Cathedral And The Bazaar" and is written by Eric Raymond.
Coming from Unix background, he was taken in surprise in 1991 by the Open Source movement and became a beliver himself by 1996. He has actually drawn heavily from the experiences he had with Linus Torvalds or Richard Stallman and these have heavily influenced his writings.
Eric is the person who popularised the line "Given Enough Eyeballs, All Bugs Are Shallow". It's actually a one line summary of the concept of a Bazaar (which is how Linux was developed)...where there is no given protocol and ANYONE can say (contribute) whereas the Cathedral mode of development is when there is a Open Source development thru guidelines and frameworks.
Also interesting to note, when you read the article you will start seeing the myriad ways in which Open Source Development is so similar to Agile SW Development Practices.
I found the following ideas of open source development very similar to that of Agile Development.
4. If you have the right attitude, interesting problems will find you.
5. When you lose interest in a program, your last duty to it is to hand it off to a competent successor.
6. Treating your users as co-developers is your least-hassle route to rapid code improvement and effective debugging.
7. Release early. Release often. And listen to your customers
8. Given a large enough beta-tester and co-developer base, almost every problem will be characterized quickly and the fix obvious to someone
10. If you treat your beta-testers as if they're your most valuable resource, they will respond by becoming your most valuable resource.
11. The next best thing to having good ideas is recognizing good ideas from your users. Sometimes the latter is better.
13. ``Perfection (in design) is achieved not when there is nothing more to add, but rather when there is nothing more to take away.''
18. To solve an interesting problem, start by finding a problem that is interesting to you
19: Provided the development coordinator has a medium at least as good as the Internet, and knows how to lead without coercion, many heads are inevitably better than one
So much for today...see you soon
Subscribe to:
Posts (Atom)