[thelist] Web Dev Program

Anthony Baratta anthony at baratta.com
Mon Jul 9 12:54:12 CDT 2007

Ahhhh... Grasshopper - we have much to learn about the way of code. ;-)

<tip author="Anthony Baratta" type="Comments and Logging in Code">

As a good designer and coder you should be commenting your code for future reference. If not for yourself, for others to follow up later with. But what about logging?

Depending on the coding language and platform, you should also be building logging options to your code. With the flip of a boolean or the setting of a string you can have your inline logging collecting and spitting out data for your perusal.

The few extra minutes it takes to write a line or two, or make a conditional call to your logging functions at strategic locations within your code is time well spent as your application becomes larger and more complex.


-----Original message-----
From: j s jslist at sbcglobal.net
Date: Mon, 09 Jul 2007 10:17:02 -0700
To: "thelist at lists.evolt.org" thelist at lists.evolt.org
Subject: Re: [thelist] Web Dev Program

> Yes it's easier to keep things consistent when you modularize components.  And I definetly understand if your doing a shopping cart the line count would be low.  This is more complicated stuff.  The down side is when big chunks of the asp code are compartmentalized debugging isn't alot of fun.  
> Thanks for the suggestions.

More information about the thelist mailing list