---- START NEW MESSAGE --- Received: from cherry.ease.lsoft.com [209.119.0.109] by dpmail10.doteasy.com with ESMTP (SMTPD32-8.05) id A086CAB0216; Sun, 01 Feb 2004 19:14:14 -0800 Received: from PEAR.EASE.LSOFT.COM (209.119.0.19) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <4.00CC84EA@cherry.ease.lsoft.com>; 1 Feb 2004 22:14:08 -0500 Received: from MITVMA.MIT.EDU by MITVMA.MIT.EDU (LISTSERV-TCP/IP release 1.8e) with spool id 7505 for PICLIST@MITVMA.MIT.EDU; Sun, 1 Feb 2004 22:14:01 -0500 Received: from MITVMA (NJE origin SMTP@MITVMA) by MITVMA.MIT.EDU (LMail V1.2d/1.8d) with BSMTP id 0676; Sun, 1 Feb 2004 22:12:20 -0500 Received: from gull.mail.pas.earthlink.net [207.217.120.84] by mitvma.mit.edu (IBM VM SMTP Level 430) via TCP with ESMTP ; Sun, 01 Feb 2004 22:12:19 EST X-Comment: mitvma.mit.edu: Mail was sent by gull.mail.pas.earthlink.net Received: from user-0c994j1.cable.mindspring.com ([24.148.146.97] helo=xppro) by gull.mail.pas.earthlink.net with smtp (Exim 3.33 #1) id 1AnUVa-0005DD-00 for PICLIST@MITVMA.MIT.EDU; Sun, 01 Feb 2004 19:12:22 -0800 References: <2193429B07D9914D97216EBBAA6AB8BD1A0509@whitlam.corp.gli.com.au> <5.2.0.9.2.20040129073858.01554480@mail.cedar.net> <5.2.0.9.2.20040129124239.015f7178@mail.cedar.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Message-ID: <009101c3e93b$03c41430$0100a8c0@xppro> Date: Sun, 1 Feb 2004 22:16:56 -0500 Reply-To: pic microcontroller discussion list Sender: pic microcontroller discussion list From: John Ferrell Subject: Re: [PIC:] Process To: PICLIST@MITVMA.MIT.EDU Precedence: list X-RCPT-TO: Status: U X-UIDL: 371856798 There has been a wealth of great advice here. Let me add my thoughts. Read code from many sources and evaluate the style from the standpoint of how easy it is for you to read and understand. The next step is to imitate the style until you are comfortable with it. Evaluate your bugs and other problems and try to find "a better way for you" and test the personal enhancements. AFTER you are comfortable with that favored style THEN consider innovations. Be consistent in your documentation and style. If you take a different tack for every project, don't expect to improve. I think the leveling off that is typical for programmers is because they find a way that works, they are reluctant to look for some thing better. If you have access to high level languages that will allow you better labor efficiency, I can think of no reason to avoid them. John Ferrell 6241 Phillippi Rd Julian NC 27283 Phone: (336)685-9606 johnferrell@earthlink.net http://DixieNC.US NSRCA 479 AMA 4190 W8CCW "My Competition is Not My Enemy" ----- Original Message ----- From: "Dave VanHorn" To: Sent: Thursday, January 29, 2004 12:46 PM Subject: Re: [PIC:] Process >> >This isn't what you wanted to hear, but frankly, if you've been coding for a > >while and you haven't already developed your own idea of how to do it > >carefully and right you never will. This isn't meant as an insult, just a > >true belief on my part. I'm going to catch a lot of heat for this, but my > >advice is to find something else to do that you are truly good at. > > Hmm.. It sounds like you're saying that one can't improve, and I have to > reject that. > I can always get better.. > > >For what little it's worth, my idea of a better environment and methodology > >for writing PIC assembler code is at http://www.embedinc.com/pic. > > Digesting. > > -- > http://www.piclist.com hint: The PICList is archived three different > ways. See http://www.piclist.com/#archives for details. > -- http://www.piclist.com hint: PICList Posts must start with ONE topic: [PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads .