• Steve Jones - SSC Editor - Thursday, March 14, 2019 11:39 AM

    There are definitely issues with management, but there is also time involved to get people to learn to be better. That is something that should happen, but it can't happen on day 1. No organization I know of is also willing to sit a new hire down for days or weeks to learn to be better until they start writing production code.

    Plenty of organizations also need to hire people, which can be hard to do. Some hold out, but some need bodies to get work done, and that's understandable. Some of those bodies will write poor code as they learn and grow, and some senior people will help them learn, but it's always a challenge.

    It would be great to do everything right the first time, or at least do most things right, but many of us don't agree on right in every case, so it's not really a reality. We should strive to be better, but not everyone does and that's also reality. We don't get to hire just the stars or even the "I want to be a star". There are people that work 9 to 5, in this industry and every other one.

    I get that but when you hire someone that claims 10 years of experience and you're hiring for a senior position, there should be little excuse for not doing it right the first time but the company won't actually know that they're going to have a problem because, thanks to Microsoft Marketing, everyone and their brother think they know SQL Server and, especially, T-SQL because they can actually do an INNER JOIN based on more than one column.

    And, yes.... it absolutely does take time to get people to learn better but a whole lot of companies simply don't make that investment because they supposedly hired only senior people.  Remember my question about how to get the current date and time using T-SQL and how I quite counting after 20 out of 22 people couldn't answer the question?  Remember also that they all claimed senior experience on the resume and job history and that they supposed got that experience while working at another company.

    People keep saying that their code is "good enough" but how the hell would they know?  They're a part of the group that fail the current date and time question.

    And I'm not talking about people needing to become rock stars but I am talking about people with more than 5 years of experience not even knowing the bloody basics.

    There's something really broken out there if "Good enough" has become the standard because "Good enough" usually isn't and few have to foresight to understand that rework costs 8 times or more than simply doing it right the first time.

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