Are the posted questions getting worse?

  • Yeah, a serious lesson for all to be had in doing unto others...

    David

    @SQLTentmaker

    “He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot

  • Nothing is off topic, and as long as someone responds, might as well keep it going here.

    I agree with Jack, too much loosey-goosey activity with retirement funds. I tend to lean Libertarian, but I think this is one area that government has to provide some shelter, AND not be allowed to touch it. FICA might not be bad shape if the money were just left there. It's politicians that think it's being wasted by sitting there. It's security, not an investment fund.

    Breaking promises to retirees is a bad sign. It means they suffer, and it means we can't trust you if we're younger. Too many people and companies are breaking their promises, gambling to try and make another buck. That part of my country embarrasses me.

  • Oh, and shouldn't is the case, but can't should be in there. Modifying the contract, especially once the workers don't have any leverage, is both ethically wrong, and should be legally prohibited.

    Arguing that you'll be able to better return the money to retirees later shouldn't be allowed either. The reason is that if you fail, it's no skin off your back. And the company can declare bankruptcy, and the taxpayers pick up part of the bill. But real people suffer.

    If you can't run your company or goverment without the funds set aside for retirement, then you can't do the things you want to. You have to cut back. Better now than in the future.

  • Jack Corbett (12/9/2008)


    Looks like someone to some persons fell in love with UDF's.

    Developer1 - "Hey why write it over and over again, we can encapsulate it in a UDF and now we have re-usable code"

    Developer2 - "Wow, you are genius! Why didn't I think of that?"

    Developer3 - "This will cut our development time by 20%, more time on the internet!'

    That is awesome Jack.. I actually have heard the programmers here say that, nearly verbatim.

  • David Lester (12/26/2008)


    Jack Corbett (12/9/2008)


    Looks like someone to some persons fell in love with UDF's.

    Developer1 - "Hey why write it over and over again, we can encapsulate it in a UDF and now we have re-usable code"

    Developer2 - "Wow, you are genius! Why didn't I think of that?"

    Developer3 - "This will cut our development time by 20%, more time on the internet!'

    That is awesome Jack.. I actually have heard the programmers here say that, nearly verbatim.

    The scary part is that I thought like that when UDF's first came out. Then you learn, if you want to, how they work and how they can negatively impact performance and you don't mind re-writing the same code over again.

  • As Steve said:

    Arguing that you'll be able to better return the money to retirees later shouldn't be allowed either. The reason is that if you fail, it's no skin off your back. And the company can declare bankruptcy, and the taxpayers pick up part of the bill. But real people suffer.

    The irony and shame of all this is that the high and mighty executive layers still has gotten and will be paid multimillion $$ bonus' - for what -- driving a company to failure. Hey can I get a pay raise each time I write some T-SQL that uses cursors and triangular joins and takes forever to run, tying up the server so no one else can get anything done?

    If everything seems to be going well, you have obviously overlooked something.

    Ron

    Please help us, help you -before posting a question please read[/url]
    Before posting a performance problem please read[/url]

  • bitbucket (12/26/2008)


    Hey can I get a pay raise each time I write some T-SQL that uses cursors and triangular joins and takes forever to run, tying up the server so no one else can get anything done?

    According to the number of people on this forum that think it's OK to use a cursor if you're in a schedule crunch and can't think of a good set based solution, you should be able to... 😉

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

  • Jack Corbett (12/26/2008)


    David Lester (12/26/2008)


    Jack Corbett (12/9/2008)


    Looks like someone to some persons fell in love with UDF's.

    Developer1 - "Hey why write it over and over again, we can encapsulate it in a UDF and now we have re-usable code"

    Developer2 - "Wow, you are genius! Why didn't I think of that?"

    Developer3 - "This will cut our development time by 20%, more time on the internet!'

    That is awesome Jack.. I actually have heard the programmers here say that, nearly verbatim.

    The scary part is that I thought like that when UDF's first came out. Then you learn, if you want to, how they work and how they can negatively impact performance and you don't mind re-writing the same code over again.

    ...'you learn, if you want to,'...

    Haha, love it.

    This place has always hired developers who treat DB's as little more than an input file.

    I am sure we all see that at sometime. None so far have choose to learn.

    I noticed posts for favorite bad code, this has to be my personal favorite, used to dynamically build SQL (ugh)

    Dim SQLText as String

    Dim AndWhere as String --Global of course

    SQLText = 'Select field1, field2, field3 From Sometable'

    --Add 30 lines of code here

    AndWhere = 'Where'

    --Add 50 lines of code here

    SQLText = SQLText + AndWhere + ' (Field1 = 'Joe') '

    --Add 5 lines of code here

    AndWhere = 'And'

    --Add 10 lines of code here

    SQLText = SQLText + AndWhere + ' (Field2 = 'Bob') '

    AndWhere? Seriously, and being global one never could be sure what the app was putting in

    the variable. :crazy:

  • Heh... Now, now, David... it's set up perfectly for an SQL Injection attack... what are you crabbin' about? 😛

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

  • Michael Valentine Jones (12/23/2008)


    If there is someone doing a DBA interview that doesn’t have the technical understanding to be able to weed out a bogus DBA, then they probably shouldn’t be in their position.

    I went to an interview once that was simply an HR person who spent the whole time asking me definitions of IT industry buzz words. I soon realized that what this company wanted to hire was consultants who could use buzz word knowledge to be able to BS their potential clients. I didn't get the job, but I have had the pleasure several times since of subjecting their consultants to extremely hostile and humiliating interviews before showing them the door when they wanted to work on projects for my current employer. Pay back and all that…

    Don't be too sure about that. I remember interviewing this guy once who never got an answer wrong. He could talk all day long about the databases. We brought him on the team. When he sat down in front of the computer, it was pretty clear he hadn't really worked with one before. He couldn't do anything. I turned him away from the screen and the mouse (which he had been poking with one finger like it was going to bite him) and asked him how to do what he was trying to do. He reeled it off perfectly, then I turned him around and he was lost again. It was like he had memorized every option possible and knew them, but had never done them.

    We implemented practical tests after that as well. It was weird, and the exception, but it could happen.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

  • Grant Fritchey (12/27/2008)


    Don't be too sure about that. I remember interviewing this guy once who never got an answer wrong. He could talk all day long about the databases. We brought him on the team. When he sat down in front of the computer, it was pretty clear he hadn't really worked with one before. He couldn't do anything. I turned him away from the screen and the mouse (which he had been poking with one finger like it was going to bite him) and asked him how to do what he was trying to do. He reeled it off perfectly, then I turned him around and he was lost again. It was like he had memorized every option possible and knew them, but had never done them.

    We implemented practical tests after that as well. It was weird, and the exception, but it could happen.

    I'd have kept him as a Business Analyst or a Systems Analyst/Designer!

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

  • BWAAA-HAAA! Excellent candidate for this year's SQL Darwin award...

    http://www.sqlservercentral.com/Forums/Topic478330-8-1.aspx#BM480712

    Scroll up from that post to see the hell he caused a bunch of people because he thought Sybase and SQL Server worked the same what. 😛

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

  • Grant Fritchey (12/27/2008)


    Don't be too sure about that. I remember interviewing this guy once who never got an answer wrong. He could talk all day long about the databases. We brought him on the team. When he sat down in front of the computer, it was pretty clear he hadn't really worked with one before. He couldn't do anything. I turned him away from the screen and the mouse (which he had been poking with one finger like it was going to bite him) and asked him how to do what he was trying to do. He reeled it off perfectly, then I turned him around and he was lost again. It was like he had memorized every option possible and knew them, but had never done them.

    Heh, now I would've hired him as a consultant. I can teach anyone how to use a mouse. But, telling other people how to do something? That's really hard. 🙂

    [font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
    Proactive Performance Solutions, Inc.
    [/font]
    [font="Verdana"] "Performance is our middle name."[/font]

  • Jeff Moden (12/27/2008)


    BWAAA-HAAA! Excellent candidate for this year's SQL Darwin award...

    He's a repeat offender who just doesn't seem to get it. I have several unpleasant memories of that guy's posts.

    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 (12/27/2008)


    Jeff Moden (12/27/2008)


    BWAAA-HAAA! Excellent candidate for this year's SQL Darwin award...

    He's a repeat offender who just doesn't seem to get it. I have several unpleasant memories of that guy's posts.

    Heh... yeah... I've been following his posts for about a year because of the things he asks... he tries real hard but, like you said, he really doesn't get it, yet.

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

Viewing 15 posts - 496 through 510 (of 66,712 total)

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