Hi Roy,

<< Writing a lot of code fast is easy. The difficult bit is writing good quality code either fast or slow!

Even more difficult is writing smaller amounts of good quality code to do the same job as a lot of mediocre quality code. >>

Yeah, I know what you mean.  I've been coding full-time for close to 20 years.  Looking through the EWB units, Tim produces a lot of complex code very quickly, which is very impressive.  He's like a guy I work with who can produce huge, complex (but very efficient) stored procedures in SQL Server in a matter of a couple of hours.  It would take me days to do the same thing.

Steve

<I call this phase of development the "kick in the nuts" phase.  You spend months doing development, and then
get to hear every little thing that is wrong with what you just slaved over. >

We only bother telling you what's wrong because we see the value and know you can make it indispensable... - it sure is better than slaving over something and finding out that no-one cares about it one bit.

Ron,

<< We only bother telling you what's wrong because we see the value and know
you can make it indispensable... - it sure is better than slaving over
something and finding out that no-one cares about it one bit.  >>

Absolutely, and please don't take my comments in the wrong way.  It's mostly
just human nature to be disappointed when you think you've got it all
correct and working properly, only to find out that, no sir, you do not.

--
Tim Young
Elevate Software
www.elevatesoft.com

Steve

>Yeah, I know what you mean. I've been coding full-time for close to 20 years. Looking through the EWB units, Tim produces a lot of complex code very quickly, which is very impressive. He's like a guy I work with who can produce huge, complex (but very efficient) stored procedures in SQL Server in a matter of a couple of hours. It would take me days to do the same thing.

Fully agree - just don't expect me to debug it

Roy Lambert

Tim

>Thank you, comments like that mean a lot. I call this phase of development
>the "kick in the nuts" phase. You spend months doing development, and then
>get to hear every little thing that is wrong with what you just slaved over.
>

Brilliant assessment. Must remember that for personal use.

Roy Lambert