Here are the bullets from Carl's designer tip sheet that may be useful:
1. forget the past 2. think simple 3. scripts start with a header 4. data drives it 5. names are critical 6. use words not strings 7. code in style 8. examples save time 9. learn series 10. embed your documentation 11. define the problem 12. use the shell 13. dialects are key 14. take advantage of return values. Some of the items listed by the responses are here and they are all important but for starters: 11. Define the problem 12. use the shell .... test in the console 9. learn series 4. data drives your program (which is possible when you have #9) 6. use words not strings 5. names are critical And look at the sample code in the library. -- To unsubscribe from this list, just send an email to [EMAIL PROTECTED] with unsubscribe as the subject.
