Are the posted questions getting worse?

  • CirquedeSQLeil (9/17/2010)


    Has anybody else noticed how close SSC is to 1 million posts overall?

    Any bets on if we could get that done by the end of the year?

    Only ~12000 posts to go.

    Heh... and more than 1/50th of those are mine. ๐Ÿ˜€ Have you noticed that once you get past the 20k mark, no one notices anymore? ๐Ÿ˜›

    --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)

  • Trey Staker (9/17/2010)


    CirquedeSQLeil (9/17/2010)


    Just curious if anybody here has ever walked out of an interview...What would be your justifications for doing so?

    I've never walked out on an interview but had one guy walk out on us during it. He thought he was going to be a lone wolf DBA and when he realized the position was to be a member of a team the interviewee stood up and just walked away.

    Why would anyone want to be the lone wolf DBA? Having been in that position for a few months due to a re-org, I can't imagine doing it for any length of time and keeping my sanity intact.

    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.

  • Heh... this place is going to hell in a handbasket. I got a shirt for going over 3k. I got a shirt for going over 5k. I got two copies of Best of SQL Server for free on my first article. Since then... nothing. Not even for busting the 20K barrier. And I'd really like the copies of "Best of" that my articles appear in. The "Contributors" page say I should get some... did none of my articles make it?:hehe:

    --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)

  • Stefan Krzywicki (9/17/2010)


    GilaMonster (9/17/2010)


    Jeff Moden (9/17/2010)


    GilaMonster (9/17/2010)


    Steve Jones - Editor (9/17/2010)


    Too slow! Removing a lot of SPAM this morning, and disabling some accounts.

    Yeah, there was quite a collection this morning. I think I made like 10 post reports over breakfast

    I reported some as well... they all started with something like "Hi, me glad to be her. This good place to...." and then it had a link at the bottom for a movie site (IIRC).

    Most of the ones I found were certification spam. 'This site will answer all your cert related questions, including exams, braindumps, admin, backups, rfid, ...'

    (or search engine keyword heaven)

    One of many reasons I find certifications to have little value. Same with interview tests.

    I'll second that.

    --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)

  • Tom.Thomson (9/17/2010)


    Jeff Moden (9/17/2010)


    ... DBAs and DBA's are both acceptable ...

    Surely not socially?

    Unless perhaps it's a case of Angelic possession.

    Heh... you tell me... they let Steve out to have a beer with a client. Does that count? ๐Ÿ˜€

    --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)

  • Jeff Moden (9/17/2010)


    CirquedeSQLeil (9/17/2010)


    Trey Staker (9/17/2010)


    CirquedeSQLeil (9/17/2010)


    Just curious if anybody here has ever walked out of an interview...What would be your justifications for doing so?

    I've never walked out on an interview but had one guy walk out on us during it. He thought he was going to be a lone wolf DBA and when he realized the position was to be a member of a team the interviewee stood up and just walked away. We did have a few minutes of interview time and had pretty much assesed that he wasn't qualified. The sad part is he probably found a job somewhere as a DBA.

    That is quite unfortunate. I prefer the team environment.

    Speaking of teams... congrats on breaking the 10K point barrier. You haven't shown up on the "post" leader board yet but you are in a fairly elite group of 6 folks to ever get 10K points and 1 or those is Steve Jones. ๐Ÿ˜›

    Thanks - would you believe I am #9 on that post board? Just a few more points there.

    Jason...AKA CirqueDeSQLeil
    _______________________________________________
    I have given a name to my pain...MCM SQL Server, MVP
    SQL RNNR
    Posting Performance Based Questions - Gail Shaw[/url]
    Learn Extended Events

  • Jeff Moden (9/17/2010)


    CirquedeSQLeil (9/17/2010)


    Has anybody else noticed how close SSC is to 1 million posts overall?

    Any bets on if we could get that done by the end of the year?

    Only ~12000 posts to go.

    Heh... and more than 1/50th of those are mine. ๐Ÿ˜€ Have you noticed that once you get past the 20k mark, no one notices anymore? ๐Ÿ˜›

    Nobody knows what to do up in that rarefied air. Only other person with you (for now) is an employee. Maybe they just figure you are too? Threadizens know better.

    Jason...AKA CirqueDeSQLeil
    _______________________________________________
    I have given a name to my pain...MCM SQL Server, MVP
    SQL RNNR
    Posting Performance Based Questions - Gail Shaw[/url]
    Learn Extended Events

  • Brandie Tarvin (9/17/2010)


    Trey Staker (9/17/2010)


    CirquedeSQLeil (9/17/2010)


    Just curious if anybody here has ever walked out of an interview...What would be your justifications for doing so?

    I've never walked out on an interview but had one guy walk out on us during it. He thought he was going to be a lone wolf DBA and when he realized the position was to be a member of a team the interviewee stood up and just walked away.

    Why would anyone want to be the lone wolf DBA? Having been in that position for a few months due to a re-org, I can't imagine doing it for any length of time and keeping my sanity intact.

    It is no fun being the lone wolf. Work work work all the time and nobody to share it with. I think it grinds after a while.

    Jason...AKA CirqueDeSQLeil
    _______________________________________________
    I have given a name to my pain...MCM SQL Server, MVP
    SQL RNNR
    Posting Performance Based Questions - Gail Shaw[/url]
    Learn Extended Events

  • CirquedeSQLeil (9/17/2010)


    Brandie Tarvin (9/17/2010)


    Trey Staker (9/17/2010)


    CirquedeSQLeil (9/17/2010)


    Just curious if anybody here has ever walked out of an interview...What would be your justifications for doing so?

    I've never walked out on an interview but had one guy walk out on us during it. He thought he was going to be a lone wolf DBA and when he realized the position was to be a member of a team the interviewee stood up and just walked away.

    Why would anyone want to be the lone wolf DBA? Having been in that position for a few months due to a re-org, I can't imagine doing it for any length of time and keeping my sanity intact.

    It is no fun being the lone wolf. Work work work all the time and nobody to share it with. I think it grinds after a while.

    The worst is you're permanently on-call. Noone to share the load of bad data loads, someone tripping on the powercords, or there to help reset the snapshot on transactional replication when your raid-5 double drive fails... Spent the entire Easter weekend dealing with that one once, double plus ungood.

    I've walked out of a few interviews, mostly younger in life and non-SQL related, but one that sticks out was when the pay was poor and they were trying to leverage all of my skillset instead of just letting me be a mindless code monkey (I scale my contractor pay to the job description). When I brought up that the job was more detailed and higher level then I had originally discussed with my consulting firm and would need to renegotiate, he literally said: "What, you expect to get paid for the things you only do 50% of the time?" I figured further discussion would be pointless. I excused myself and contacted the firm that I wouldn't be attempting to work with that client, and they should review the job description, it required x, y, and z.


    - Craig Farrell

    Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.

    For better assistance in answering your questions[/url] | Forum Netiquette
    For index/tuning help, follow these directions.[/url] |Tally Tables[/url]

    Twitter: @AnyWayDBA

  • GSquared (9/1/2010)


    Here's an interesting one. This is the list of skills someone wants for their "DBA":

    Must have advanced proficiency and extensive knowledge of web development and design technologies, and publishing , experience in designing web-based applications in PHP, ColdFusion and ASP.NET, expert level skills in Microsoft SQL Server, MySQL, Stored Procedure development, and Object Data Base Connections (ODBC) and DTS as well as experience defining and creating complex Web Services. Requires expert level skills in JavaScript, HTML and CSS, extensive understanding of XML and related technologies, plus expert level understanding of web protocols such as HTTP, HTTPS, FTP, and SMTP, SSL and encryption technologies as they relate to e-commerce. Requires extensive understanding of ColdFusion and SQL Server software installation procedures as well as expert level skills in database backup and recovery. Also requires use and detailed understanding of Streaming Video encoding applications and Players, particularly Windows Media Encoder/Player and Flash COM Server. Advanced skills in Macromedia development tools and standard desktop applications such as MS Office also required. Must be able to successfully handle multiple tasks/projects and have excellent technical writing skills (including requirements, specifications, status reports, flowcharts and project plans).

    All I can say is, "ummmm...."

    Why does this just scream... SQL 2000 in a small shop?

    All you need now is ability to type 75 words/minute and makes a mean cup of coffee, and you have then entire office staff covered. ๐Ÿ™‚

    ----------------------------------------------------------------------------------
    Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?

  • Craig Farrell (9/17/2010)


    CirquedeSQLeil (9/17/2010)


    Brandie Tarvin (9/17/2010)


    Trey Staker (9/17/2010)


    CirquedeSQLeil (9/17/2010)


    Just curious if anybody here has ever walked out of an interview...What would be your justifications for doing so?

    I've never walked out on an interview but had one guy walk out on us during it. He thought he was going to be a lone wolf DBA and when he realized the position was to be a member of a team the interviewee stood up and just walked away.

    Why would anyone want to be the lone wolf DBA? Having been in that position for a few months due to a re-org, I can't imagine doing it for any length of time and keeping my sanity intact.

    It is no fun being the lone wolf. Work work work all the time and nobody to share it with. I think it grinds after a while.

    The worst is you're permanently on-call. Noone to share the load of bad data loads, someone tripping on the powercords, or there to help reset the snapshot on transactional replication when your raid-5 double drive fails... Spent the entire Easter weekend dealing with that one once, double plus ungood.

    I've walked out of a few interviews, mostly younger in life and non-SQL related, but one that sticks out was when the pay was poor and they were trying to leverage all of my skillset instead of just letting me be a mindless code monkey (I scale my contractor pay to the job description). When I brought up that the job was more detailed and higher level then I had originally discussed with my consulting firm and would need to renegotiate, he literally said: "What, you expect to get paid for the things you only do 50% of the time?" I figured further discussion would be pointless. I excused myself and contacted the firm that I wouldn't be attempting to work with that client, and they should review the job description, it required x, y, and z.

    This is one of the reasons (there are many others :-)) I tend to stay away from DBA tasks and concentrate on development, design, interfacing, performance, etc... I don't like being on-call!

    --------------------------------------
    When you encounter a problem, if the solution isn't readily evident go back to the start and check your assumptions.
    --------------------------------------
    Itโ€™s unpleasantly like being drunk.
    Whatโ€™s so unpleasant about being drunk?
    You ask a glass of water. -- Douglas Adams

  • Brandie Tarvin (9/17/2010)


    Why would anyone want to be the lone wolf DBA?

    To avoid having to put up with other DBAs.

  • Stefan Krzywicki (9/17/2010)


    Craig Farrell (9/17/2010)


    CirquedeSQLeil (9/17/2010)


    Brandie Tarvin (9/17/2010)


    Trey Staker (9/17/2010)


    CirquedeSQLeil (9/17/2010)


    Just curious if anybody here has ever walked out of an interview...What would be your justifications for doing so?

    I've never walked out on an interview but had one guy walk out on us during it. He thought he was going to be a lone wolf DBA and when he realized the position was to be a member of a team the interviewee stood up and just walked away.

    Why would anyone want to be the lone wolf DBA? Having been in that position for a few months due to a re-org, I can't imagine doing it for any length of time and keeping my sanity intact.

    It is no fun being the lone wolf. Work work work all the time and nobody to share it with. I think it grinds after a while.

    The worst is you're permanently on-call. Noone to share the load of bad data loads, someone tripping on the powercords, or there to help reset the snapshot on transactional replication when your raid-5 double drive fails... Spent the entire Easter weekend dealing with that one once, double plus ungood.

    I've walked out of a few interviews, mostly younger in life and non-SQL related, but one that sticks out was when the pay was poor and they were trying to leverage all of my skillset instead of just letting me be a mindless code monkey (I scale my contractor pay to the job description). When I brought up that the job was more detailed and higher level then I had originally discussed with my consulting firm and would need to renegotiate, he literally said: "What, you expect to get paid for the things you only do 50% of the time?" I figured further discussion would be pointless. I excused myself and contacted the firm that I wouldn't be attempting to work with that client, and they should review the job description, it required x, y, and z.

    This is one of the reasons (there are many others :-)) I tend to stay away from DBA tasks and concentrate on development, design, interfacing, performance, etc... I don't like being on-call!

    When I've been in a small shop as an employee being a developer/designer didn't get you off the call schedule. Where I worked everyone in the IT department took a turn as the on-call person and that person was the point person for problems who then called the next person if needed. Let's just say I learned a lot about documentation while I was there.:-P

  • Jack Corbett (9/18/2010)


    Stefan Krzywicki (9/17/2010)


    Craig Farrell (9/17/2010)


    CirquedeSQLeil (9/17/2010)


    Brandie Tarvin (9/17/2010)


    Trey Staker (9/17/2010)


    CirquedeSQLeil (9/17/2010)


    Just curious if anybody here has ever walked out of an interview...What would be your justifications for doing so?

    I've never walked out on an interview but had one guy walk out on us during it. He thought he was going to be a lone wolf DBA and when he realized the position was to be a member of a team the interviewee stood up and just walked away.

    Why would anyone want to be the lone wolf DBA? Having been in that position for a few months due to a re-org, I can't imagine doing it for any length of time and keeping my sanity intact.

    It is no fun being the lone wolf. Work work work all the time and nobody to share it with. I think it grinds after a while.

    The worst is you're permanently on-call. Noone to share the load of bad data loads, someone tripping on the powercords, or there to help reset the snapshot on transactional replication when your raid-5 double drive fails... Spent the entire Easter weekend dealing with that one once, double plus ungood.

    I've walked out of a few interviews, mostly younger in life and non-SQL related, but one that sticks out was when the pay was poor and they were trying to leverage all of my skillset instead of just letting me be a mindless code monkey (I scale my contractor pay to the job description). When I brought up that the job was more detailed and higher level then I had originally discussed with my consulting firm and would need to renegotiate, he literally said: "What, you expect to get paid for the things you only do 50% of the time?" I figured further discussion would be pointless. I excused myself and contacted the firm that I wouldn't be attempting to work with that client, and they should review the job description, it required x, y, and z.

    This is one of the reasons (there are many others :-)) I tend to stay away from DBA tasks and concentrate on development, design, interfacing, performance, etc... I don't like being on-call!

    When I've been in a small shop as an employee being a developer/designer didn't get you off the call schedule. Where I worked everyone in the IT department took a turn as the on-call person and that person was the point person for problems who then called the next person if needed. Let's just say I learned a lot about documentation while I was there.:-P

    I'll bet! I always wonder if the documentation I write on each contract is ever used again after I leave.

    As a contractor, most places don't want me to be on-call 'cause they don't want to pay overtime.

    --------------------------------------
    When you encounter a problem, if the solution isn't readily evident go back to the start and check your assumptions.
    --------------------------------------
    Itโ€™s unpleasantly like being drunk.
    Whatโ€™s so unpleasant about being drunk?
    You ask a glass of water. -- Douglas Adams

  • Stefan Krzywicki (9/18/2010)


    Jack Corbett (9/18/2010)


    When I've been in a small shop as an employee being a developer/designer didn't get you off the call schedule. Where I worked everyone in the IT department took a turn as the on-call person and that person was the point person for problems who then called the next person if needed. Let's just say I learned a lot about documentation while I was there.:-P

    I'll bet! I always wonder if the documentation I write on each contract is ever used again after I leave.

    As a contractor, most places don't want me to be on-call 'cause they don't want to pay overtime.

    I wouldn't say that everyone read the documentation, but I had it for myself, and I did point people to it when they'd call me. I'd say, "Did you look in the Knowledge Base? I documented how to handle that issue. If that doesn't help call me back".

    On-call is one reason I'd prefer to be a contractor/consultant if I ever leave my current workplace.

Viewing 15 posts - 18,946 through 18,960 (of 66,712 total)

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