>>>>Taking the horse to the water, cute, but try to make him swim on his back :)
>>>>
>>>>p.s. Is it "politically correct" to call us programmers? I don't like the term "developer" - for me, it represents a bottle of brownish liquid. I used to spend many hours in the photo lab :)
>>>
>>>ROFL...
>>>I knew I wouldn't be able to make the thirsty horse analogy in this forum without someone taking it alot farther :) Good old Dragan to the rescue! BTW great comments too!!
>>>
>>>As far as politically correct to call us programmers vs. developers, well if I could manage to figure out how to keep my nose stuck in code all day long and not get caught up in design, documentation, planning, and deep intellectual discussion of emerging technology trends - I too would prefer to be called a programmer instead of developer. But since I can not figure out how to do that, I figure a flashy title like "developer" is better suited to one who does a little bit of everything. Just my opinion though.
>>
>>Are you trying to say that you would rather keep your nose in the programming screen? It sounds that way-- and I would say that the best way to do that would be to forget all those USELESS THREADS AND BOOKS like this and just do it.
>>
>
>Whoa Jeff, it's not that this is what I truly wish for, but you know sometimes you have those days where you can't help thinking the pipe dream of "how could I make my life simplier". :) Just to put my comment into context a little more, I changed jobs a few months ago. Old job I was a 1 man show stuck with a neverending FPW legacy app. And I did so many different things other than coding that all I wanted was to get back to being a programmer. I have a new job now, and it took this change to get me finally using VFP and I'm busting my butt to catch up with the industry(or so it seems). And yes of course, you can't just stick you're nose in code and still be a good programmer, but boy if I could just do that for a few months right now I could get my skill level up to my knowledge level and my work would be alot more satisfying. But of course I can't do that - My hunger for knowledge is too ambitious. But keeping my nose stuck in code wasn't really my point here, my point was it takes
>so much non-coding work and responsibility to be a good programmer these days so I think the title "developer" is alot more fitting.


I guess I should have put a :) or <bg>. Seems You might have taken me even remotely seriously. I was not. I was in my own pitiful way trying to be funny. Guess I didn't make it uh?

Jeff