[ActiveLock-Development] Coding Standard (was Re: Meeting Tonight)

[Thanh H. T. <th...@sy...>]

Dan,
I took liberty of replying to the list  because I thought the whole could
benefit from our conversation....
Anyway, good job on completing the code.  Very much appreciated for your
help.
I should mention (I thought it goes without saying) that as a developer you
are responsible for testing your own code, and a good way of doing it is
through the test program.  That way, you 1) make sure that your changes
doesn't break existing code, and 2) demonstrate to others that your stuff
works.  I don't expect anyone's code to be bug-free, but on the other hand,
I don't want people leaving bugs in the code that are notoriously due to
carelessness or lack of testing. I'm no exception.  I'd be the first one to
kick myself in the behind if I ever do such a thing.
No one else is going to go out of their way to unit test our code for us so
we must do it ourselves.

Sorry, I don't mean to sound harsh, but our code is going to be used by many
people all over the world.  So we must strive to maintain a professional
level of coding ethics throughout, because the end result of that is that
you have a high quality, kick-ass piece of code that everyone will admire.
:)

So Dan, please go ahead and make the appropriate changes in the test app to
make it work with your changes. If you need clarification on how the stuff
works, please let me know.

Regards,
Thanh.

----- Original Message ----- 
From: "Dan" <wiz...@us...>
To: <th...@us...>
Sent: Monday, July 28, 2003 9:38 PM
Subject: Meeting Tonight


> Cc: <wiz...@us...>
> Message-Id: <E19...@sc...>
> Date: Mon, 28 Jul 2003 18:15:48 -0700
> X-EA-Verified: mxrelay.vasoftware.com 19hJ62-0006YT-Gk
554d897e6c5f393c85e2d75c31cca85e
> X-Spam-Score: 0.7
>
>
> [stuffs snipped] Anyway, I thought about my
> problem and decided that maybe I don't even have to worry
> about it. I finished all of the required code and customizations
> within half an hour, debugged and all, and then I want to test
> it for real. The code to test it needs heavy modification to be
> able to use the changes. I'm thinking that I was never told to
> do that, so maybe thats not my job. Anyway, the only real
> problem now is that the test app fails to register properly and
> always comes back as unregistered when you restart the
> program. I am going to assume that there is a MD5 check or
> something that is messing it up. I have not spent much time
> checking into that yet.