if you have no clue what you are talking about, don't bother saying a word
January 24th, 2002I understand that some people don't know more than others. I understand that some people are just ignorant in regard to certain matters, and I can handle that. In fact, I enjoy that, because it gives me an opportunity to teach them, and to feel accomplished when I see them doing well. However, I become very disgusted at people who are ignorant regarding a particular topic, and yet INSIST that they are right.
Case in point:
I have been working with an individual who wrote an application (and I use that phrase VERY loosely) that is backed by a Microsoft SQL server. His application serves the same function as an application my group has developed. His users are unwilling to switch to our application, so, for reporting purposes, he has to feed me data from his system so I can account for his information.
After three or four attempts to get the data correct, I suggest a pseudo-SQL statement (not having any clue what his tables or fields look like) that will get the job done. He responds telling me that my VERY simple query will utilize too much CPU time and that he is doing it a different way. I ask him to send me his SQL, which he does. After examining his SQL, not only am I able to determine WHY the data he is sending is incorrect, but it is also very apparent that my SQL statement would be far less CPU intensive… especially considering his claim that MSSQLv4 doesn't handle date functions very well (which… I can neither confirm nor deny having never used it), as my query makes ONE date comparison, while his makes THREE.
Why would this individual tell me that my query would take up too much CPU when he actually has NO clue.
