Re: anti-advocacy: Larry Seltzer, pcmag May'01 pub.

I suppose you could look at it that way, but actually, since VB isn't case-sensitive, it wouldn't matter how I typed it as long as I spell it right. So it's not like a spell checker correcting my spelling. Rather, it's like a word processor applying the paragraph style for me instead of me having to set my indents & tab stops manually each time. Actually it does turn out to be both a productivity aid & verification tool. It's faster because I don't have to shift case as I type & it verifies, because if I see that it doesn't apply the proper case, I get immediate feedback that I've mistyped the variable/function name. It would catch it anyway when it compiles the code (just as C would catch an undefined variable), but I don't have to wait till the compile step to correct it - I can do it right there! There are a number of things that MS does wrong, but this part at least they've got very right. -- Greg "Bradley Miller" <bradmiller@accesszone.com> wrote in message news:3.0.3.32.20010510101438.00a06af0@mail.accesszone.com... > Ok -- this too is not a flame, but just an opinion. I personally don't > exactly like that much hand holding. It's like the "auto-correct" features > in MS products. Yea, it's great for productivity and that . . . but what > reinforces the thought that you boo-boo'ed and didn't have to correct it? > If I spell receive as "recieve" every time I type something . . . it's > still not right in my mind . . . otherwise I wouldn't type it. When you > don't have the crutch of the computer handy -- are you going to look like a > complete moron with all the "learned" typos that MS corrected for you? > Tools should not instill bad practices and mask them for you. They are > tools -- just that . . . they should enable you to work easier, but they > shouldn't fix your work for you -- at least not automatically to where the > conditioned response is "typos are good as long as the computer figures it > out". > > -- Bradley Miller