Re: Buying an upload component
[re: wives] that's how I found mine!
She started cleaning three minutes after getting into my rented house and I
thought to myself 'that's the woman for me'. Joking of course, my wife is
amazing and even puts up with me tapping away at 2am in the morning if
something grabs me.
Chris.
"Jeff Cochran" <jcochran.nospa m@naplesgov.com > wrote in message
news:3f9b7384.6 04256835@msnews .microsoft.com. ..[color=blue]
>NB: I was following this thread since I've never done uploads but I'd like
>to in the near future and I thought I might learn something. However, it
>looks like I'll just have to get hold of them all and have a go myself to
>see what's best for me - probably a component, not for speed, but for speed
>and ease of development.[/color]
That's really the key, finding what works for you. In some cases, we
use the absolute worst product for the job simply because we're
comfortable programming with it. In my case, I usually test the first
component I find, if I can understand it and comfortably work with it
within three minutes, I don't normally look at the next one.
Sometimes it takes a few tries, sometimes you get lucky right out of
the gate. But you would never get anything productive done if you
agonized over every choice you made and examined all the what-if's
involved.
Works the same with wives... :)
Jeff
[re: wives] that's how I found mine!
She started cleaning three minutes after getting into my rented house and I
thought to myself 'that's the woman for me'. Joking of course, my wife is
amazing and even puts up with me tapping away at 2am in the morning if
something grabs me.
Chris.
"Jeff Cochran" <jcochran.nospa m@naplesgov.com > wrote in message
news:3f9b7384.6 04256835@msnews .microsoft.com. ..[color=blue]
>NB: I was following this thread since I've never done uploads but I'd like
>to in the near future and I thought I might learn something. However, it
>looks like I'll just have to get hold of them all and have a go myself to
>see what's best for me - probably a component, not for speed, but for speed
>and ease of development.[/color]
That's really the key, finding what works for you. In some cases, we
use the absolute worst product for the job simply because we're
comfortable programming with it. In my case, I usually test the first
component I find, if I can understand it and comfortably work with it
within three minutes, I don't normally look at the next one.
Sometimes it takes a few tries, sometimes you get lucky right out of
the gate. But you would never get anything productive done if you
agonized over every choice you made and examined all the what-if's
involved.
Works the same with wives... :)
Jeff
Comment