Are the posted questions getting worse?

  • Heh... that reminds me of an old poem about denial...

    Roses are Red,

    Violets are Blue,

    Some Poems Rhyme,

    But this one don't.

    😀

    --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)
    Intro to Tally Tables and Functions

  • david.edwards 76768 wrote:

    I've registered for the EightKB event, so I can tune in to Jeff's session. Had the confirmation email but no details on how to join. Are these sent closer to the time?

    I sure hope so.

    --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)
    Intro to Tally Tables and Functions

  • Anyone know a full stack developer looking for a job at a good company? We're looking for several and haven't got great candidates (some good but with little to zero experience).

    Preferrably in the Atlanta area, or willing to relocate, but anywhere in the US could work.

    The job description

    Luis C.
    General Disclaimer:
    Are you seriously taking the advice and code from someone from the internet without testing it? Do you at least understand it? Or can it easily kill your server?

    How to post data/code on a forum to get the best help: Option 1 / Option 2
  • Some good but with little to no experience???  Dude, suck them up and train them before someone corrupts them. 😀

    --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)
    Intro to Tally Tables and Functions

  • Luis Cazares wrote:

    Anyone know a full stack developer looking for a job at a good company? We're looking for several and haven't got great candidates (some good but with little to zero experience).

    Preferrably in the Atlanta area, or willing to relocate, but anywhere in the US could work.

    The job description

    I have been a full stack asp.net developer since .net 1.1 and there are a few things on this list of experiences I have never heard of and several that I have never used. No offense meant but a laundry list with that many experience preferences is a HUGE red flag to me. When I read that it sounds like you want a senior developer with tons of experience who is also going to be doing their own design (both code and database), testing, reporting, security and administration.

    _______________________________________________________________

    Need help? Help us help you.

    Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.

    Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.

    Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
    Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
    Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
    Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/

  • Jeff Moden wrote:

    Ed Wagner wrote:

    Jeff Moden wrote:

    That might also be the reason why they've done the RBAR thing in the trigger.  They don't want to have everything during and Insert or Update roll back if something isn't right and so try to handle it row by row.  Is it an "Instead of" trigger by any chance?

    Good point, Jeff. That's actually a strong argument to treat it as a set. The transaction should either completely work or not work, not partially work. That's how an ACID DB transaction is supposed to work. By doing RBAR in a trigger, they're allowing a transaction to partially work. In the immortal words of Yoda, "Do or do not. There is no try." 😀

    Heh... you know me, Ed... "King of the Edge Cases".  There's some really strong exceptions to that.  Here's a real-life exception I've personally run into... and wrote code for as a "help" to someone else last night.

    You receive a file of 30 million CDRs (Call Detail Records).  Even in this day and age, there can be the proverbial burp in a system that drops a byte or two without damaging the file beyond usage.  It just damages one CDR.  Billing of such calls is the lifeblood of the company and the PUC has certain rules about how long you have to actually bill calls not to mention that you have customers that want to do a weekly or maybe even daily analysis of calls.

    Should you really reject all 30 million calls just because one call has a burp in it and everything else is perfect?  Or, do you sequester that CDR for secondary analysis and correction a couple of hours from now and let all the other good CDRs fly on schedule as expected?

    "It Depends" 😀

    Jeff, in your case 30 mil CDRs are separate records which don't depend on each other, therefore it's 30 mil transaction, not a single 30 mil long transaction.

    Unless the file contains some aggregations in its header/footer sections, like total number or records, which means that the source system has those aggregations recorded as submitted, and the file may be accepted or rejected as whole. Otherwise total numbers will be not in sync in the source and target systems.

    _____________
    Code for TallyGenerator

  • Luis Cazares wrote:

    Anyone know a full stack developer looking for a job at a good company? We're looking for several and haven't got great candidates (some good but with little to zero experience).

    Preferrably in the Atlanta area, or willing to relocate, but anywhere in the US could work.

    The job description

    If you're looking for several, it's better to look for specialists which are good in certain areas, not full stack developers which memorised systax of all the scripting languages but are good at nothing in particular.

     

     

    _____________
    Code for TallyGenerator

  • Sean Lange wrote:

    Luis Cazares wrote:

    Anyone know a full stack developer looking for a job at a good company? We're looking for several and haven't got great candidates (some good but with little to zero experience).

    Preferrably in the Atlanta area, or willing to relocate, but anywhere in the US could work.

    The job description

    I have been a full stack asp.net developer since .net 1.1 and there are a few things on this list of experiences I have never heard of and several that I have never used. No offense meant but a laundry list with that many experience preferences is a HUGE red flag to me. When I read that it sounds like you want a senior developer with tons of experience who is also going to be doing their own design (both code and database), testing, reporting, security and administration.

    It's desired experience, not required. As mentioned, we might be getting to junior developers that would need tons of mentoring. Also, those are the technologies being used, but no one is expected to know them all. Some of the "local experts" are still learning on how to use them correctly. Technologies can be taught/learned, but attitude is hard to change.

    Luis C.
    General Disclaimer:
    Are you seriously taking the advice and code from someone from the internet without testing it? Do you at least understand it? Or can it easily kill your server?

    How to post data/code on a forum to get the best help: Option 1 / Option 2
  • Sergiy wrote:

    Jeff Moden wrote:

    Ed Wagner wrote:

    Jeff Moden wrote:

    That might also be the reason why they've done the RBAR thing in the trigger.  They don't want to have everything during and Insert or Update roll back if something isn't right and so try to handle it row by row.  Is it an "Instead of" trigger by any chance?

    Good point, Jeff. That's actually a strong argument to treat it as a set. The transaction should either completely work or not work, not partially work. That's how an ACID DB transaction is supposed to work. By doing RBAR in a trigger, they're allowing a transaction to partially work. In the immortal words of Yoda, "Do or do not. There is no try." 😀

    Heh... you know me, Ed... "King of the Edge Cases".  There's some really strong exceptions to that.  Here's a real-life exception I've personally run into... and wrote code for as a "help" to someone else last night.

    You receive a file of 30 million CDRs (Call Detail Records).  Even in this day and age, there can be the proverbial burp in a system that drops a byte or two without damaging the file beyond usage.  It just damages one CDR.  Billing of such calls is the lifeblood of the company and the PUC has certain rules about how long you have to actually bill calls not to mention that you have customers that want to do a weekly or maybe even daily analysis of calls.

    Should you really reject all 30 million calls just because one call has a burp in it and everything else is perfect?  Or, do you sequester that CDR for secondary analysis and correction a couple of hours from now and let all the other good CDRs fly on schedule as expected?

    "It Depends" 😀

    Jeff, in your case 30 mil CDRs are separate records which don't depend on each other, therefore it's 30 mil transaction, not a single 30 mil long transaction.

    Unless the file contains some aggregations in its header/footer sections, like total number or records, which means that the source system has those aggregations recorded as submitted, and the file may be accepted or rejected as whole. Otherwise total numbers will be not in sync in the source and target systems.

    Do you have an actual example of a 30 million row transaction where every row was actually required or you had to fail all 30 million rows?  I'm not looking for something hypothetical... I'm looking for an actual example that you've personally experienced.

    --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)
    Intro to Tally Tables and Functions

  • Luis Cazares wrote:

    Sean Lange wrote:

    Luis Cazares wrote:

    Anyone know a full stack developer looking for a job at a good company? We're looking for several and haven't got great candidates (some good but with little to zero experience).

    Preferrably in the Atlanta area, or willing to relocate, but anywhere in the US could work.

    The job description

    I have been a full stack asp.net developer since .net 1.1 and there are a few things on this list of experiences I have never heard of and several that I have never used. No offense meant but a laundry list with that many experience preferences is a HUGE red flag to me. When I read that it sounds like you want a senior developer with tons of experience who is also going to be doing their own design (both code and database), testing, reporting, security and administration.

    It's desired experience, not required. As mentioned, we might be getting to junior developers that would need tons of mentoring. Also, those are the technologies being used, but no one is expected to know them all. Some of the "local experts" are still learning on how to use them correctly. Technologies can be taught/learned, but attitude is hard to change.

    I totally agree about attitude and ability to learn. My point is that the list is so big I have a feeling you are chasing away people you might not want to. I see that list and don't want to explore it further because I can't check off enough boxes. Of course I am not really in the job market either as I am pretty happy where I am at. I do know a couple people that are looking, I will send them your way.

    _______________________________________________________________

    Need help? Help us help you.

    Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.

    Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.

    Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
    Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
    Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
    Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/

  • Sean Lange wrote:

    My point is that the list is so big I have a feeling you are chasing away people you might not want to. I see that list and don't want to explore it further because I can't check off enough boxes.

    +1

    That list scared the bejesus out of me :-/

    Far away is close at hand in the images of elsewhere.
    Anon.

  • When I see that list, I'm not at all scared. I've seen many descriptions, not just in tech, but in medicine, legal, hospitality, etc. where a job ad is created by a committee. It's a chore, so the person doing it asks others, and ends up with lots of "wishes", but not requirements.

    I've always told people if you hit 50% of the skills, apply. Likely they would like someone to have them all, but they know it's not possible, so they can train you on the things you don't know if you are a good candidate.

    Likely any project you are on contains only a portion of those skills, so this isn't any different than many descriptions I've seen. If that kind of things scares you, likely you are letting opportunities go by.

  • Steve Jones - SSC Editor wrote:

    When I see that list, I'm not at all scared. I've seen many descriptions, not just in tech, but in medicine, legal, hospitality, etc. where a job ad is created by a committee. It's a chore, so the person doing it asks others, and ends up with lots of "wishes", but not requirements.

    I've always told people if you hit 50% of the skills, apply. Likely they would like someone to have them all, but they know it's not possible, so they can train you on the things you don't know if you are a good candidate.

    Likely any project you are on contains only a portion of those skills, so this isn't any different than many descriptions I've seen. If that kind of things scares you, likely you are letting opportunities go by.

    The point is, such litanies keep even good people from applying for one of two reasons...

    1. The list is overwhelming to people that don't know it's a wish list.
    2. Other people look at it and say that if they can't properly distinguish between requirements and "nice to haves", they might suck as a place to work for because they can't define what they actually need are so they take the shotgun approach.

    --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)
    Intro to Tally Tables and Functions

  • Steve Jones - SSC Editor wrote:

    When I see that list, I'm not at all scared. I've seen many descriptions, not just in tech, but in medicine, legal, hospitality, etc. where a job ad is created by a committee. It's a chore, so the person doing it asks others, and ends up with lots of "wishes", but not requirements.

    I've always told people if you hit 50% of the skills, apply. Likely they would like someone to have them all, but they know it's not possible, so they can train you on the things you don't know if you are a good candidate.

    Likely any project you are on contains only a portion of those skills, so this isn't any different than many descriptions I've seen. If that kind of things scares you, likely you are letting opportunities go by.

    That list would not have scared me off when I was looking 5+ years ago.  I took a list like that as a wish list.  I would say I applied for jobs when I had less than 50% of the skills.  I figured they could weed me out if I didn't have enough of what they needed.

    -------------------------------------------------------------
    we travel not to escape life but for life not to escape us
    Don't fear failure, fear regret.

  • Jeff Moden wrote:

    Steve Jones - SSC Editor wrote:

    When I see that list, I'm not at all scared. I've seen many descriptions, not just in tech, but in medicine, legal, hospitality, etc. where a job ad is created by a committee. It's a chore, so the person doing it asks others, and ends up with lots of "wishes", but not requirements.

    I've always told people if you hit 50% of the skills, apply. Likely they would like someone to have them all, but they know it's not possible, so they can train you on the things you don't know if you are a good candidate.

    Likely any project you are on contains only a portion of those skills, so this isn't any different than many descriptions I've seen. If that kind of things scares you, likely you are letting opportunities go by.

    The point is, such litanies keep even good people from applying for one of two reasons...

    1. The list is overwhelming to people that don't know it's a wish list.
    2. Other people look at it and say that if they can't properly distinguish between requirements and "nice to haves", they might suck as a place to work for because they can't define what they actually need are so they take the shotgun approach.

    Even knowing it is a wish list it is a bit overwhelming. Makes me nervous the expectations are way high.

    On the topic of not being able to distinguish requirements from "nice to haves" this is a shining example. There is both a "Desired Experience" and "Requirements Qualifications" sections. But then under the requirements you see "Experience with TDD is a plus". It's on the wrong list which is another potential warning sign.

    So to Steve's point, maybe this would be me missing a good opportunity. Or perhaps Jeff is right that it scared away a good person. There is no right or wrong here, I just gave my opinion that it made me shy away because it seems to be looking for too much.

    Sorry to pick this one apart Luis. I know you were posting here hoping to find some leads, not a critique of the posting that you didn't write. Hopefully you are able to find somebody soon.

    _______________________________________________________________

    Need help? Help us help you.

    Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.

    Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.

    Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
    Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
    Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
    Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/

Viewing 15 posts - 65,521 through 65,535 (of 65,837 total)

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