On Monday, April 29, 2002, at 09:53 , Timothy Johnson wrote:
> I'd definitely have to agree with you on that one. As much as it may seem
> so when under the influence, none of us are can put out good code without
> thinking about it, and alcohol is definitely not conducive to lucid
> thought.
> This also applies to uppers, downers, crack, smack, and beanie babies.
Allow me to pass along what I call "Tween's Law" -
If it is a good idea
then it will still be a good idea in the morning.
Most folks forget that the their higher order analytics
are the first to go as they get 'exhausted' - and the
efforts to pump up with stimulants - including any
of the variants on 'horsing the problem' or 'win
one for the gipper' - do not change that process.
{ which include TESTOSTERONE POISONING!!! "me butch,
me manly, me hunt down and kill little bug in code...." }
all work against coders.
There is a point in the process where you just have to
'let it go' step back away from it all, and put some
distance between you and the problem.
Rather than proceed along to inject new and improved
bugs because you are simply not thinking straight.
As such project management needs to start with the
coders and a clear understanding on their part about
how much coding they can actually do in a day before
they are merely writing bugs...
ciao
drieux
---
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
