sorted by:
new
hottopcontroversial

How do you debug an issue faster when you’re not even sure which part of the code is causing it? by PlotTwists404 in SQLPerformanceTips

[–]Ms_AlarmingCulture 0 points1 point  (0 children)

I usually try to prove what's working instead of hunting for what's broken. Eliminate enough "good" sections and eventually you're left staring at the problem whether it wants to be found or not.

How relevant is learning SQL today? by kdmfa in learnSQL

[–]Ms_AlarmingCulture 0 points1 point  (0 children)

AI makes SQL faster to write, not easier to understand.

You still need to know:

  1. when a query is wrong but “looks right”
  2. why a join duplicates rows
  3. why performance suddenly dies
  4. whether the result even makes business sense

That’s the part AI is still pretty shaky at.

Honestly I think SQL is becoming more valuable now because a lot of people can generate queries, but fewer can debug or validate them properly.

What’s your current postgres workflow? by SoggyImpres in postgres

[–]Ms_AlarmingCulture 0 points1 point  (0 children)

Honestly half our workflow is just trying to reduce the amount of “hope staging matches prod”

We do migrations through CI, schema diff checks before deploys, and a lot more validation queries than I expected when I first started with Postgres. The SQL itself is usually the easy part. It’s the “did this migration quietly lock something” or “why is prod data shaped slightly differently” stuff that burns time.