Are the posted questions getting worse?

  • djj (11/16/2015)


    I will be the first to admit I am not the smartest person, but at least I try to ask questions by providing requested information with my try at the problem. When answering questions, I try to get the person to show at least a little work but usually they do not.

    I've lost count of the number of times I've prepared the material to explain a question, only to have found the answer in doing so.

    SSC is my rubber duck.

  • GilaMonster (11/14/2015)


    I am getting seriously tired of the lack of thought and understanding evidenced by recent questions from certain individuals. Is a little bit of independent work and research really too much to ask?

    Can you use it as a teachable moment? Maybe the second time you observe the lack of thought?

    412-977-3526 call/text

  • BrainDonor (11/16/2015)


    djj (11/16/2015)


    I will be the first to admit I am not the smartest person, but at least I try to ask questions by providing requested information with my try at the problem. When answering questions, I try to get the person to show at least a little work but usually they do not.

    I've lost count of the number of times I've prepared the material to explain a question, only to have found the answer in doing so.

    SSC is my rubber duck.

    That's a hidden gem in preparing a question. There was a discussion in a thread somewhere about how preparing consumable DDL, sample data and expected results really helps people (myself included) strip a problem down to its wires and isolate it from everything else. That helps me to see the problem.

  • Ed Wagner (11/16/2015)


    BrainDonor (11/16/2015)


    djj (11/16/2015)


    I will be the first to admit I am not the smartest person, but at least I try to ask questions by providing requested information with my try at the problem. When answering questions, I try to get the person to show at least a little work but usually they do not.

    I've lost count of the number of times I've prepared the material to explain a question, only to have found the answer in doing so.

    SSC is my rubber duck.

    That's a hidden gem in preparing a question. There was a discussion in a thread somewhere about how preparing consumable DDL, sample data and expected results really helps people (myself included) strip a problem down to its wires and isolate it from everything else. That helps me to see the problem.

    And then there are the times where I strip a problem to the wires, the issue is staring me in the face, and I still don't see that missing paren or comma.

    Brandie Tarvin, MCITP Database AdministratorLiveJournal Blog: http://brandietarvin.livejournal.com/[/url]On LinkedIn!, Google+, and Twitter.Freelance Writer: ShadowrunLatchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.

  • Brandie Tarvin (11/16/2015)


    Ed Wagner (11/16/2015)


    BrainDonor (11/16/2015)


    djj (11/16/2015)


    I will be the first to admit I am not the smartest person, but at least I try to ask questions by providing requested information with my try at the problem. When answering questions, I try to get the person to show at least a little work but usually they do not.

    I've lost count of the number of times I've prepared the material to explain a question, only to have found the answer in doing so.

    SSC is my rubber duck.

    That's a hidden gem in preparing a question. There was a discussion in a thread somewhere about how preparing consumable DDL, sample data and expected results really helps people (myself included) strip a problem down to its wires and isolate it from everything else. That helps me to see the problem.

    And then there are the times where I strip a problem to the wires, the issue is staring me in the face, and I still don't see that missing paren or comma.

    Been there, done that. 😀

  • djj (11/16/2015)


    Brandie Tarvin (11/16/2015)


    Ed Wagner (11/16/2015)


    BrainDonor (11/16/2015)


    djj (11/16/2015)


    I will be the first to admit I am not the smartest person, but at least I try to ask questions by providing requested information with my try at the problem. When answering questions, I try to get the person to show at least a little work but usually they do not.

    I've lost count of the number of times I've prepared the material to explain a question, only to have found the answer in doing so.

    SSC is my rubber duck.

    That's a hidden gem in preparing a question. There was a discussion in a thread somewhere about how preparing consumable DDL, sample data and expected results really helps people (myself included) strip a problem down to its wires and isolate it from everything else. That helps me to see the problem.

    And then there are the times where I strip a problem to the wires, the issue is staring me in the face, and I still don't see that missing paren or comma.

    Been there, done that. 😀

    ....and probably doing it tomorrow.....:-)

    😎

  • robert.sterbal 56890 (11/16/2015)


    Can you use it as a teachable moment? Maybe the second time you observe the lack of thought?

    Second? Well past 20th in the two cases that triggered that post.

    Stuff like "I want to do X, will it help with Y?" Reply with "No, and why are you doing X in the first place?" Reply: "I read somewhere you should do X", and repeatedly, no thinking about why one would do X, no research into whether doing X is the general guideline or just one person's opinion

    Or "I'm getting an alert saying that X counter is greater than Y, what should I do?"

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • Brandie Tarvin (11/16/2015)


    Ed Wagner (11/16/2015)


    BrainDonor (11/16/2015)


    djj (11/16/2015)


    I will be the first to admit I am not the smartest person, but at least I try to ask questions by providing requested information with my try at the problem. When answering questions, I try to get the person to show at least a little work but usually they do not.

    I've lost count of the number of times I've prepared the material to explain a question, only to have found the answer in doing so.

    SSC is my rubber duck.

    That's a hidden gem in preparing a question. There was a discussion in a thread somewhere about how preparing consumable DDL, sample data and expected results really helps people (myself included) strip a problem down to its wires and isolate it from everything else. That helps me to see the problem.

    And then there are the times where I strip a problem to the wires, the issue is staring me in the face, and I still don't see that missing paren or comma.

    Sure, but I'm betting you're not going to just post the entire original problem here and say "There's a syntax error with this."

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • GilaMonster (11/16/2015)


    robert.sterbal 56890 (11/16/2015)


    Can you use it as a teachable moment? Maybe the second time you observe the lack of thought?

    Second? Well past 20th in the two cases that triggered that post.

    Stuff like "I want to do X, will it help with Y?" Reply with "No, and why are you doing X in the first place?" Reply: "I read somewhere you should do X", and repeatedly, no thinking about why one would do X, no research into whether doing X is the general guideline or just one person's opinion

    Or "I'm getting an alert saying that X counter is greater than Y, what should I do?"

    After 3 teachable moments, you should enlist help with the teaching.

    412-977-3526 call/text

  • GilaMonster (11/16/2015)


    Brandie Tarvin (11/16/2015)


    Ed Wagner (11/16/2015)


    BrainDonor (11/16/2015)


    djj (11/16/2015)


    I will be the first to admit I am not the smartest person, but at least I try to ask questions by providing requested information with my try at the problem. When answering questions, I try to get the person to show at least a little work but usually they do not.

    I've lost count of the number of times I've prepared the material to explain a question, only to have found the answer in doing so.

    SSC is my rubber duck.

    That's a hidden gem in preparing a question. There was a discussion in a thread somewhere about how preparing consumable DDL, sample data and expected results really helps people (myself included) strip a problem down to its wires and isolate it from everything else. That helps me to see the problem.

    And then there are the times where I strip a problem to the wires, the issue is staring me in the face, and I still don't see that missing paren or comma.

    Sure, but I'm betting you're not going to just post the entire original problem here and say "There's a syntax error with this."

    I'm betting you're right, but I know what you mean. I've seen some of those. Some are just so plain dumb that you wonder if they even read their own code in the first place or if they just posted it blindly.

  • Ed Wagner (11/16/2015)


    GilaMonster (11/16/2015)


    Brandie Tarvin (11/16/2015)


    Ed Wagner (11/16/2015)


    BrainDonor (11/16/2015)


    djj (11/16/2015)


    I will be the first to admit I am not the smartest person, but at least I try to ask questions by providing requested information with my try at the problem. When answering questions, I try to get the person to show at least a little work but usually they do not.

    I've lost count of the number of times I've prepared the material to explain a question, only to have found the answer in doing so.

    SSC is my rubber duck.

    That's a hidden gem in preparing a question. There was a discussion in a thread somewhere about how preparing consumable DDL, sample data and expected results really helps people (myself included) strip a problem down to its wires and isolate it from everything else. That helps me to see the problem.

    And then there are the times where I strip a problem to the wires, the issue is staring me in the face, and I still don't see that missing paren or comma.

    Sure, but I'm betting you're not going to just post the entire original problem here and say "There's a syntax error with this."

    I'm betting you're right, but I know what you mean. I've seen some of those. Some are just so plain dumb that you wonder if they even read their own code in the first place or if they just posted it blindly.

    Goes further than just code, how about a raise of hands, 30+ indices on a narrow table all which are named _DTA_xxxx

    😎

  • Ed Wagner (11/16/2015)


    GilaMonster (11/16/2015)


    Brandie Tarvin (11/16/2015)


    Ed Wagner (11/16/2015)


    BrainDonor (11/16/2015)


    djj (11/16/2015)


    I will be the first to admit I am not the smartest person, but at least I try to ask questions by providing requested information with my try at the problem. When answering questions, I try to get the person to show at least a little work but usually they do not.

    I've lost count of the number of times I've prepared the material to explain a question, only to have found the answer in doing so.

    SSC is my rubber duck.

    That's a hidden gem in preparing a question. There was a discussion in a thread somewhere about how preparing consumable DDL, sample data and expected results really helps people (myself included) strip a problem down to its wires and isolate it from everything else. That helps me to see the problem.

    And then there are the times where I strip a problem to the wires, the issue is staring me in the face, and I still don't see that missing paren or comma.

    Sure, but I'm betting you're not going to just post the entire original problem here and say "There's a syntax error with this."

    I'm betting you're right, but I know what you mean. I've seen some of those. Some are just so plain dumb that you wonder if they even read their own code in the first place or if they just posted it blindly.

    Actually, I did once. I was using dynamic SQL, had my "Exec @var" and couldn't figure out what was going wrong with it.

    Someone kindly pointed out that it should have been "Exec (@var)" and I turned redder than a beet with embarrassment for spamming the forums for that particular mistake.

    Brandie Tarvin, MCITP Database AdministratorLiveJournal Blog: http://brandietarvin.livejournal.com/[/url]On LinkedIn!, Google+, and Twitter.Freelance Writer: ShadowrunLatchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.

  • BrainDonor (11/16/2015)


    djj (11/16/2015)


    I will be the first to admit I am not the smartest person, but at least I try to ask questions by providing requested information with my try at the problem. When answering questions, I try to get the person to show at least a little work but usually they do not.

    I've lost count of the number of times I've prepared the material to explain a question, only to have found the answer in doing so.

    SSC is my rubber duck.

    Those are the type of questions you should still post along with your answer. One, someone else may have a similar issue. Two, you may be surprised and see your solution get tweaked and improved.

  • Sorry, got snippy with an OP.

    50 lashes with a noodle please.

  • Jeff Moden (11/14/2015)


    To explain some of my extreme frustration in the "developers" that I've been interviewing over the last decade, the following blog post is a great example of the type of people that I've had to interview.

    http://enterprisecraftsmanship.com/2015/11/11/is-sql-a-good-place-for-business-logic/

    Let's see...

    Improperly designed table... check.

    Virtually no knowledge of T-SQL demonstrated (doesn't even know what a CASE statement is)... check.

    No knowledge of how a view works (confirmation of no T-SQL knowledge)... check.

    Improperly designed data model the whole article is based on... check.

    Typical thinking that a single row return isn't a "set" leading to not knowing how a view works... check.

    Ring-knocker attitude confirmed by attempts to justify it all by saying he used to be a database developer... check.

    Typical know-it-all chip on the shoulder... check.

    Yeah.... :blink::sick: NEXT!

    Dropped a comment in there. Was hoping for more debate.

Viewing 15 posts - 51,391 through 51,405 (of 66,712 total)

You must be logged in to reply to this topic. Login to reply