We shall code... (Important)

Hi All, I think we all have alot of good ideas, mail client, web portals, file sharing, and others. Now comes the hard part, designing not just a program, but a movement that can get from point A to point Z. It has always seemed to me that even the simplest of tasks when given to a committee, suddenly become complex issues. I suppose it is human nature to strive for perfection in different ways. Whatever the reason, I am sure most of you have witnessed such chaos many times before, and understand the troubles of group efforts. One thing I have noticed about this list, is that anytime anybody needs a hand, they get it. Some of you remember our friend "princepawn." He didn't seem to know much rebol. Almost everyday for quite awhile, he would tell us he needed to do this or that, and a bunch of us would work out how to do it, often writing little functions and such, which he probably just plugged into his program he was working on. I recall some of us wondering if he actually did any of the work. His system seemed to work quite well. As when he need help with parsing, those of us that were parsing experts would quickly come to his aid, and when it was objects he needed help with, the same thing. My recommendation is that whatever we want to work on, we do a "princepawn". We plan our programs very well, identifying areas that could be modularized. Before writing the program, or maybe after writing the shell, post to this list some of the units (functions, forms, objects, dialects, database, etc) you might like other people to write. Odds are you will get someone who has written something similar to that before, and they will do an excellent job in record time. In fact you should be able to carry out this system all the way from conception, having a GUI guru write the interface, someone multi-talented write the shell or flow chart, and so forth. Rebol is one of the best languages in the world for doing this. I bet by using this method, Rebmail could have been written within a week. --Ryan David Vydra wrote:

> I say that some of us need to choose a goal(s) and start a project or two > on sourceforge.org in search of the "Killer App". I would like to make sure > [rebol-request--rebol--com] with "unsubscribe" in the > subject, without the quotes.

Hi All, I think we all have alot of good ideas, mail client, web portals, file sharing, and others. Now comes the hard part, designing not just a program, but a movement that can get from point A to point Z. It has always seemed to me that even the simplest of tasks when given to a committee, suddenly become complex issues. I suppose it is human nature to strive for perfection in different ways. Whatever the reason, I am sure most of you have witnessed such chaos many times before, and understand the troubles of group efforts. One thing I have noticed about this list, is that anytime anybody needs a hand, they get it. Some of you remember our friend "princepawn." He didn't seem to know much rebol. Almost everyday for quite awhile, he would tell us he needed to do this or that, and a bunch of us would work out how to do it, often writing little functions and such, which he probably just plugged into his program he was working on. I recall some of us wondering if he actually did any of the work. His system seemed to work quite well. As when he need help with parsing, those of us that were parsing experts would quickly come to his aid, and when it was objects he needed help with, the same thing. My recommendation is that whatever we want to work on, we do a "princepawn". We plan our programs very well, identifying areas that could be modularized. Before writing the program, or maybe after writing the shell, post to this list some of the units (functions, forms, objects, dialects, database, etc) you might like other people to write. Odds are you will get someone who has written something similar to that before, and they will do an excellent job in record time. In fact you should be able to carry out this system all the way from conception, having a GUI guru write the interface, someone multi-talented write the shell or flow chart, and so forth. Rebol is one of the best languages in the world for doing this. I bet by using this method, Rebmail could have been written within a week. --Ryan Ryan Cole Programmer Analyst www.iesco-dms.com 707-468-5400

Hi I'm new here on the mailinglist and was surprised to find so many equal-minded people here (or maybe I'm just lucky? :-). I totally agree with you, Ryan. As a software engineer, I can't help but constantly think of the following steps in making of programs: 1. Brainstorm on ideas, features, etc. 2. Define the specification of requirements based on the brainstorm 3. Design the program, splitting it into parts as you mention 4. Code the parts 5. Document each part 5. Test each part (provided each part is testable) 6. Integrate the parts to a complete program 7. Test the program If we're smart enough, some of those parts could be designed to be reusable in future programs. Now, following the thread here, it seems the brainstorm is well under way. How about collecting this information and make it centrally available? And what about a document and code repository? Are there any standard places for this for Rebol programmers? Regards, Henrik Mikael Kristensen HMK Design On Wednesday 15 August 2001 20:06, you wrote: