I'm the type of girl that can write a 100-line SQL migration without autocomplete, AI and copying-and-pasting and make it run correctly on the first try.

That’s good for you and bad for SQL :)

Am I turned on right now?

Will you marry me?

And I'm the kind of man that makes his backend lackey do that.

We are not the same. He does what I tell him to do.

@BobbyTables welcome back!

Wife material

Without autocomplete is the only way you write that shit because SQL is so hostile to both static analysis and typing aids that pretty much the only things you can get hints on are column names but only in SELECT and only from existing tables, and in EXEC if you're very careful with surrounding syntax to not fuck up the parser.

So far the best SQL autocomplete I've seen is Azure Data Studio's, and given the fantastic quality autocomplete the MS language team can make, I'll believe they tried their best, but it's even worse than Ruby's, which is the other language that decided to wage a war on common sense and static analysis for no fucking reason.