neil

  • 12 Posts
  • 73 Comments
Joined 1 year ago
cake
Cake day: June 13th, 2023

help-circle





  • Like others said: sql, sql, sql. The syntax is probably easier than excel, but a lot of people stink at it because they don’t want to invest in the spatial reasoning required to make it work magic, and that opens doors to easy opportunity.

    If you can get into a position like reporting or data quality, and be “that person” that fixes a dreaded slow query to make it run in milliseconds instead of minutes, then you’ll get your proverbial blank check to go where you want. Those queries exist in just about every business.

    Take a look around for “sql portfolio projects” for more complete stuff that goes beyond tutorials.








  • Thought I might follow up since I had an interview today - I never stop interviewing - and was asked about duration. My off-the-cuff response was “if a company invests in its employees, offers growth and promotes internally, then I will work for a place longer. If it does not and only offers a dead-end role with no appreciable growth, then I will look for that opportunity elsewhere.”




  • Man, SSIS really stunk. You’d end up having to write your own components anyways and had the extra layer of making them look like pricey RAD toolkit bits to satisfy empty suits. And then you’d have to write SSIS packages that wrote SSIS packages to deal with fluid schemas from multiple teams deploying all of the time.






  • Generally the most supported language on the tool/platform you want to target is the best one. Like SQL on databases, JS/ES in browsers, python in data science related stuff, etc. If multiple are heavily supported then just pick the one that’s the most comfortable.