Post reply

Job requires X years of SQL... How do you respond?

  • March 11, 2025 at 9:07 pm

    #4557256

    I can't even tell you how many jobs I've seen that require "X years of SQL experience".  How do you know when you're near what that would be? For me, that's a nonsense metric. In theory, at one job, I did 8 months of SQL stuff, when in reality, I did the same things over and over for the first six or eight weeks, and then I told them that if I fixed their database design, their data problems would mostly go away. (But then I've been playing with fake relational databases like Abscess since 1996 or so, so I'm not a total noob... I just happen not to like Access very much.)

    The hideous Sales / Manufacturing mess I've been tormenting you all with (Sorry, it's hard!) has been nuts, but I've learned a ton. (And quite a lot had nothing to do with databases at all!) So how do I figure out what I still need to learn? It's not like anybody tells you, because by the time a job is posted, it's gone through several revisions where they add jobspeak and maybe whitewash the original requirements.

    So is my best option to do something like do the whole analysis and post everything on GitHub? (So a database with enough data to show I know what I'm talking about?) and then any reports or whatever I did with it (SSRS, PowerBI, etc)?

    Thanks!

  • March 12, 2025 at 9:10 pm

    #4558188

    Thanks for posting your issue and hopefully someone will answer soon.

    This is an automated bump to increase visibility of your question.

  • March 12, 2025 at 9:33 pm

    #4558218

    Just to say it out loud... It's very likely that I'll never post anything on GitHub.  However... a lot of companies insist that if you're not adding to GitHub on a regular basis, you're not worthwhile.  Think about 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)

  • March 13, 2025 at 11:48 am

    #4558669

    We started using GitHub about 6 months ago. I like it simply because it backs up my work off site. And I like the ability to document with a wiki; we have no standard for what we use to document (and still don't). Other staff see more potential. Limiting what I'm saying publicly, but what that means is we have no standards for backup either, at least this gives me one.

    • This reply was modified 1 day, 16 hours ago by  dplaut 49149.

Viewing 4 posts - 1 through 3 (of 3 total)

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