Monday, September 14, 2009

Comments - a good habit

I've just had to re-visit an area of my application which has been static for quite some time and I was glad that I have this great habit of using comments to usefully describe code.

For a long time I've been an advocate, not only in my own code but when mentoring staff in client sites, of commenting code to describe what is actually going on.

It was so easy to go back into the code and read the comments.  I then knew exactly what was going on and why.

I've never really understood the developer who rarely comments code or, when they do, don't reflect the actual logic of the code in the comments.

On client developments useful commenting is a must - after all you have no idea who will be picking up the code for that first amendment.

Setting a deadline

Not only have I set a deadline to have the coding for PexPrint complete but I've told someone about it to make sure there's someone to say "Is it done yet?". 

End of September is the target.

I've also announced the product on my website, well when I say announced it's really a page saying that it's under development with a release date targeted as Q4 2009.  But, it's another date I've said I'm aiming for.

So now I have a lot of work to do!