Louis Davidson

@way0utwest Glad that was AI generated. I felt guilty for laughing.

Things can (almost) always be worse. Remember that. Keep things in perspective.

@JenMsft I assume we are talking primary job stuff here :). I could be writing until 2 for my blog, but not work.

What does "finish by end of day" mean to you? 👀

@SQLGene @SarahDuggers Can I agree with both statements? There are levels of interaction that I think do need to be meaningful. Like should I sit and talk about something I don’t care about for hours? But at the same time, I can’t just say “this conversation bores me, @drsql out!”

@SarahDuggers Small courtesies are how we show people they are important

This is patently untrue. There are many things I have absolutely no interest in but part of socialising is TAKING an interest (or even feining one) for that bit of conversation because it is meaninful to the other person. That's basic politeness and also basic friendship.

I love my @elgato Stream Deck (iOS version) almost as much as I love SQL Prompt.

@way0utwest I got a second number for work calls recently and I am already getting calls and I have only put it in an on-call system. Apparently the previous owner may owe a debt collector…

Sheesh. It's a spam call afternoon. Landed in Chicago and 4 calls before I left the airport. At least I can clean out the VMs (32) while in a cab

@way0utwest @SQLGene @Hesamation I would guess fire :)

@drsql @SQLGene @Hesamation I think that button is the "jump" button? Or is it "fire?

Anthropic studies how AI coding affects 52 professional developers: > the group who used AI felt “lazy” and noticed gaps in their understanding and the group which didn’t use AI felt the task was “fun” > AI significantly hurts skills formation of a new library by 17% > AI didn’t actually make people faster. the time saved on not writing code was spent interacting with AI > only people who fully delegated their work to AI were noticeably faster, but they learned the least there are three AI usage patterns that preserved learning and three that really hurt it. the first three patterns: 1. asking only conceptual questions 2. generating code, then asking follow-up questions 3. asking for explanations alongside writing code and the three patterns hurting their learning: 1. complete delegation 2. starting on their own then increasingly relying on AI 3. debugging where they asked AI to fix things without understanding why

@way0utwest @SQLGene @Hesamation I would say yes, as long as they care about the craft. If not, it will be helping them to learn nothing at all. It happens in a lot of jobs computers take over. Why do I need to know what the button does if it almost always works? Well, because “almost” :)

@SQLGene @Hesamation Like a lot of modeling we do for software, these types of studies are interesting, but they can be too abstract and lose too much of how the real world is. I still can't decide if AI is really helping juniors and orgs or not.

Lucky Europe!

@Hugo_Kornelis No. That sucks so bad.

I must share sad news. After three years, my leukemia has returned. Like the previous time, I will share details and updates through my blog. Here is what I know now. sqlserverfast.com/blog/hugo/2026…

@GFritchey Even I see that one.

Oooh, my AI buddy here just made an egregious #PostgreSQL error. Anyone spot it?

Doing some writing while I await the diagnosis of my car-lonoscopy (aka oil change and tire rotation on a car that drives well right now…though could probably use a a few tires.)

@GFritchey Sure why not!

@drsql Are you on the committee? Cool! I've got a second idea for a different radio-based presentation. Should I put that one together too?

Oh, come on event organizers. I promise, a session on radios will absolutely include all sorts of stuff about databases, specifically #PostgreSQL. Someone has to pick this session up. Please? And yeah, turned down for another event.

@GFritchey Noted!

@drsql Submitted the radio session. I'll also submit a couple of others, but you know which one I want picked.

Twitter needs a button that's "bring back that tweet I was just starting to read before you automatically refreshed."

@sqlstudent144 Pretty much!

So, is everyone in the south ready to make French toast?

Seeing some #Tsql2sday posts flowing in, and here's my response. If you are like, "whoa, wasn't that, like, last week?" It was delayed, so it STILL isn't too late if you haven't finished/posted. And doesn't need to be perfect. Example: my post: drsql.link/2026/01/20/t-s…

Learning from Mistakes: T-SQL Tuesday #194 voiceofthedba.com/2026/01/20/lea… #tsql2sday

A week late for #tsqlsday, which is my fault, but thanks for @drsql for stepping up: Start drafting your posts drsql.link/2026/01/13/t-s…

It's #TsqlTuesday time, a bit late for the new year, but mistakes will be made, which is the topic! A mistake you made and how it made you a better programmer/admin/person, ideally working with data, but all are welcome and I'll share them all next week! drsql.link/2026/01/13/t-s…