dchess

The self destruct scenario for Jev is not equivalent to the Trolley problem. The equivalent would be to ask humans whether they would redirect the trolley to kill themselves to save 5 strangers. How many would make that choice? Self-preservation is a strong instinct.

I feel like this is what delta lake and ducklake are largely solving for. And then some.

It's not particularly secure but in a pinch I just use the python standard lib server to start an http server in a folder then open up the port with ngrok temporarily to share the file. Security through obscurity for a very discreet time period works.

Sounds like your team/company needs to establish SLAs. When it comes to troubleshooting the important timelines to commit to are communication timelines. First response with X hours. Updates every Y hours/days depending on severity/priority. You'll also want a clear process for establishing the criteria for diagnosing priority and what escalation paths should be when there are roadblocks.

Have you tried Heroku? Deploying via git is pretty handy. I've mostly moved to using Dokku on the $5 tier of DigitalOcean, but the approach is simple.

What's Yuck about using aliases? I use those extensively. Is that a bad practice?

As someone that works in K-12 technology (and has for 15 years), the real monopolies aren't the tech giants, they're the Pearsons and Houghton Mifflins of the world that buy out competitors and lock school districts into platforms they can't escape without substantial migration costs.

And don't even get me started on the way they have kept education hostage to high stakes tests.

Couldn't agree more. This article fails the "so what" test. What are they recommending be done instead?

I was reminded of this resource as well since it is likewise what I use in training folks to use git. This OPs post seems to be a condensed version of Chris's advice.

I don't see the benefit of putting table names on a different line than the keyword.

How is this:

  FROM
    tablename t
  INNER JOIN
    other_table ot
  ON
    t.id = ot.id

More readable than:

  FROM tablename t
  INNER JOIN other_table ot
    ON t.id = ot.id

I agree with a lot of these recommendations, but this one irks me. Also I'd love if someone could create a nice code-formatter for SQL like Python's Black.

I usually go with one of the following: "Is there a reason you didn't do X?" or "Could you use X here?" or "Have you considered using X?"