AU is just as effective as humans at contributing to sqlite: they don't accept contributions.

Thanks for sharing that nuance. It seems one court weighed in that Claude chat wasn't accepted:

> In February 2026, Judge Jed S. Rakoff of the U.S. District Court for the Southern District of New York ruled that a defendant who pasted information—including details conveyed by his lawyers—into a public, consumer-grade AI chatbot (specifically Anthropic's Claude) completely waived his attorney-client privilege.

But maybe if you are using a transcription tool that happens to send your audio through the Anthropic APIs, the ruling would be different?

Like what cloudflare does in EmDash (the spiritual successor to WordPress).

But almost all plugins would need to be rewritten?

A production app with customer data needs a data backup/restore strategy. I'm guessing a random app server writing to a local sqlite file isn't doing that either.

In my USA high School, they started requiring graphing calculators in the 9th grade math class. You would fail most quizzes/exams without the ability to run the calculations that scientific calculators couldn't do.

I'm struggling to remember using my TI-84 in college though.

I couldn't find the source on GitHub, but somebody has helpfully scraped them a few hours ago: https://github.com/pascalandy/dotfiles/blob/main/docs/refere...

I have a small CLI script that runs JQL `text ~ "$1"` (with per-repo filters on project/component).

I don't have to switch to the browser most of the time!

So in the trolley problem, you would abstain from supporting either side? I think that's actually a choice of supporting the status quo.

You are entitled to your opinion that I'm supporting the status quo by refusing to support the abject murder and depravity of one group of people over another, who may be slightly less murderous and depraved, and I'm entitled to my opinion that you are complicit in the the murder and depravity of the people you support.

I was there when the SDET role was eliminated.

Our team of 8 SDE and 5 SDET became a team of 8 devs who also owned tons of QA frameworks. It was awful, except each tiny we deleted a test suite for not being valuable; that was awesome!

If the Azure org was flooded with senior engineers who did not have senior-level experience architecting production software... That explains a lot.

My work was careful to explain: if you associate your personal GitHub account with their work org copilot, then they are the ones who manage copilot.

If you wouldn't use your personal email account on your work computer, I don't see why you wouldn't create a new GitHub account only for work.

There have been instances where GitHub has banned users for using an email address from a custom domain. If your account is associated with an enterprise plan the chances of that happening decrease significantly. Also puts you in much better position for recourse