I've gotten "Hi" with zero other context from people of all backgrounds.

I just assume they are pig-butcherers, and never respond.

As someone that has done a lot of that work, can confirm.

I remember! Lanyrd was fantastic as someone that did a ton of community speaking before I ever did anything on a bigger stage.

It's not a great defense if you ask me, unless they're counting on the judge not knowing the difference between owning a copy of something vs. the IP and license to sell the thing.

After all, Sony isn't selling the source code and IP for Resident Evil, they're selling a copy of the packaged software.

It's not as if he's stopped working on Windows since 2000.

When you can align hyperfocus with your most beneficial vector of productivity, it's like you can accomplish anything, in half the time thought possible.

Problem is, there is no good way to direct the hyperfocus demon. It likes what it likes, it wants what it wants, and that's that.

Medication helps to save a pile of willpower/spoons/executive function safely from the demon so that we can get things that need doing done.

Nothing new under the sun

Certificate expired over 100 days ago

Looks like we need “Days without ‘Days without GitHub incident’ incident”

Where do you see that?

Common Name (CN) www.dayswithoutgithubincident.com

Organization (O) <Not Part Of Certificate>

Common Name (CN) YR1

Organization (O) Let's Encrypt

Issued On Monday, August 10, 2026 at 10:01:51 AM

Expires On Sunday, November 8, 2026 at 9:01:50 AM

also seeing an expired cert:

    Common Name
    R12
    Validity
    Not Before
    Tue, 10 Feb 2026 17:28:52 GMT
    Not After
    Mon, 11 May 2026 17:28:51 GMT

This matches what I'm seeing.

Death by natural causes

> extremely unlikely

But never zero.

Adopting anything as blind dogma is Expert Beginner territory. See also: DB table normalization.

I basically spent 2 full years removing normalization from our two projects that was originally added because devs followed best practice.

Those 2 years were to do the data migration and of course there were different priorities, if that would be priority we would do it in 1 month, but we liked to spread risk over time.

Reason was of course performance issues and not really needed joins, where normalization didn't bring any benefit.

In an ideal world the data at rest would be normalized and you’d have a view or a derived table or something when needed to make queries fast when necessary.

If you ever find a job in an ideal world, hold on for dear life and please accept my CV for consideration.

> See also: DB table normalization.

Pragmatic approach: generally end up with an average of around 2.72 normalization across all tables.