They upgraded on the Doppleglock concept

Either way, I think it's hard to define what "good" is, because we all value subtly different things. It's much easier to agree on what a piece of writing is trying to do and analyse the way it goes about doing it.

There's often a confusion between "good" and "I like".
I think it's usually best to drop the word "good" and instead use words that focus on what you actually mean.
"evocative writing"
"efficient writing"
"consistent writing"

Oh, parfait!

Also, that tradition only applies to the captain, and only if there are still living people who haven't been evacuated yet.
The captain goes down with the ship rather than escapes to safety because they're responsible for the lives of the crew and passengers.

of course bryonato plays this

One thing I sometimes do to get a "best of both worlds" approach is to say something like "inspired by X".
e.g: "My Git workflow is inspired by Trunk Based Development"
That way I get the advantage of not having to explain from scratch, while avoiding problems related to interpretations of the term.

Regarding the branding thing, when I worked for a company making "serious games" (physical therapy games using off-the-shelf motion capture devices), we would never say "serious games" when presenting the company, because we didn't want people to jump to preconceptions before hearing our pitch.

There are also the usual problems with fuzzy taxonomy, which tie back to orthodoxy. When someone says "functional programming", do they mean things like callbacks and method chaining, or are we talking Haskell nerds trying to become a character in Aphyr's "Xing the technical interview" posts?

The main dangers I see are social. Dogmatism and infighting (c.f: OOP vs FP "debates" that turn sour), orthodoxy (e.g: "that's not *true* FP"), and "branding", where adherence to the word becomes more important than the underlying principles.

Programming paradigms are a good example of this, by naming them, we're able to build upon shared foundations, discover best practices, and design higher-level frameworks around them.

I think there's value and danger in naming things like this.
The value is that you don't have to explain from the ground up every time, and because it's now A Thing, it becomes possible to recognise shared patterns and solutions.

Pour un Welsh, je recommande le Broc (place de la République) ou les Compagnons de la Grappe (vieux Lille).

Le Broc est plus classique, mais j'ai une préférence pour les Compagnons.

La carbonnade n'a jamais été mon truc, je n'ai donc pas de conseil, désolé!

our housemate has a thermos with a playing card theme, and I legit thought "nice balatro flask" to myself when i saw it

bungie is of course not obligated to hire me when making a game that draws overwhelmingly from the same design language i have refined for the last decade, but clearly my work was good enough to pillage for ideas and plaster all over their game without pay or attribution.