Hmmm. I think you’re thinking of a dreadnaught. A deadlock is a magic using class in popular roleplaying games whose game powers are granted by a powerfu, but often manipulative, patron.

Misleading title.

If my thing was public in the past, and I took it private, the old public code is still public.

That’s… How the Internet works anyway.

Edit: See Eager Eagle’s better explanation below.

TL;DR - be careful who you allow to fork your private repos. And if you need to take a public repo, which has forks, private, consider archiving the repo and doing all the new work in a new repo. Which is arguably the reasonable thing to do anyway.

Still a misleading title. This isn’t a way to break into all or even most of your private repositories.

Lunchtime, doubly so!

Yeah. That’s (arguably) the background scenario to Asimov’s book “The Naked Sun” https://en.m.wikipedia.org/wiki/The_Naked_Sun

Edit: Ooh, Django already gave a cooler link to the same: https://discuss.tchncs.de/comment/10729278

Yep. I’m old, cranky, and prone to broad statements to get reactions.

That said, for any of you all that love inheritance, I’m judging you so hard. So hard. Very judged. I probably hate your code, and your friends’ code, and your last teacher’s code. Especially your last teacher’s code.

Interfaces are great.

Inheritance is often a sign that the previous developer didn’t understand interfaces.

He died of XML factory injection pattern exposure.

Nyeeeh!

Python reimplemented the same dep management wheels 5x each, and I have no idea what common stacks look like anymore, but every time I encounter Python projects, something is always broken.

We need just one more complete re-engineering of the packaging standard. We promise to get it right, this time. No take-backs.

Exactly.

I’ve followed that guidance faithfully, for decades, and…now I’m a JavaScript expert.

TIL BitWarden is open source.

Except Debian is neither interesting nor innovative.

How dare you!? /s

Yeah. Good point.

It’s really hard to go wrong with Debian.

That’s my safe answer.

If you share more about your interests, hobbies, I might have other ideas.

I suppose, when in doubt, there’s always Linux From Scratch. It’s a very interesting experience.

READY.

Rock and stone!

Yeah! Gotta find those Long Term Stable (LTSL) life partners!

This is how I feel every time I see an overpowered “prototype” weapon in a video game that works better than the standard version.

Agreed!

There’s is a bit of clever game design in Deep Rock Galactic, which I hope catches on:

The default load out for new players is almost unarguably the best possible load-out, for that class, in the game.

As players progress, they can unlock more entertaining while objectively worse equipment, to amuse and challenge themselves.

And, I mean, of course we do. It’s hilarious because some truly challenging gameplay emerges.

And when it’s kicking my butt, I at least realize I chose that challenge for myself. I had the option to bring the good equipment that I started with, after all.

And it puts new players on more even footing with veterans. I tend to make easy missions with newbie friends harder on myself by bringing truly silly equipment load outs. It usually turns out fine, and when it goes badly for me, they feel good for rescuing a veteran. Or it goes sideways and I apologize and make slightly better equip choices for the next try.

Exactly. And configured by 5000 lines of brittle XML.

Seems inevitable, but could take awhile.

Yeah. This has a “Borders hosting their eCommerce on AWS” vibe.