As manager, I shut this conversation down via direct messages to each team member involved.
I remind them that they agreed during retro to live with the current set of decisions for exactly two weeks until next retro.
I don't dictate much, but I do dictate that Slack isn't an acceptable place for this kind of discussion, on my team.
The only related thing, that belongs in slack, on my team, is a link to the current accepted team standard - which will be open for review and changes again during next retro.
Alternately, if there's no standard for this yet then my team knows they're encouraged to wing it until we discuss at next retro.
And yeah, I've had to open an issue to revisit a variable name after retro, lol.
My team are an opinionated bunch, and they're often perfectionists.
There are plenty of bad abstractions in the wild and novices applying DRY is a common source of them.
You're both saying the same thing though. Novices aggressively apply DRY the moment a second bit of identical code appears, while experienced developers often wait for a third copy and then think about whether DRY fits.
That said, I think "don't apply DRY too aggressively is the whole point of this discussion, and the person you're replying to was kind of needlessly disagreeing.
Planet Money podcast did a bit where they followed up with people who fell for buying cheap pharmaceuticals from spam emails.
The assumption was that people paid the too good to be true prices, and then never got anything in the mail.
The weird twist was that everyone interviewed was really satisfied with the product they received.
Now, all disclaimers certainly apply: don't trust a spammer with your life, there's nothing to stop imitator scammers from joining the legitimate?! spammers, and people's satisfaction is a poor measure of drug safety and efficacy.
But it does seem like a sign that someone is doing some of this already.
Yeah. Absolutely. Even having been robbed a few times really messed with my head. I would hate to have to live with worse.
But I still figure people have a right to seek a safe place to be, and cornered people have a right to use violence, to reach a safe place.
I'll allow there might even be other times when violence might be moral, since life can get pretty complex, but I hope to live my life without having to make that call.
But I believe that when cornered is the only time a human can use violence with a totally free conscience.
It's why Sun Tzu advised we always give even our worst enemy an escape route. It's much better to not have to fight at all, than to have to win a fight with a desperate enemy.
Later, baby's first words were: "Look, ma! I want to cut you in on the take, but you gotta help me be sure you won't squeal when the feds come around."
Yeah. I'm imagining Sharknado production levels and Sharknado pacing, but following the Hallmark formula, and with really mundane absurdist details.
Those fragile little precious moments figurines and limited edition Star Trek ornaments need to be a recurring favored snack for the competing love interests who are lovable but wrong for our heroes.
One of those little Christmas village decorations sets needs to turn out to be an undiscovered life saving medication, when ground down to a fine glittery paste. Feeding it to someone's niece gives her the strength to learn to walk again.
Someone's talent for cross stitch needs to solve a decades old mystery about someone else's estranged and now tragically dead parent.
A poorly gifted and then ignored-for-years art set needs to be part of the big "they truly love me" reveal moment.
That's why I buy myself projects that frustrate me for several days, before they make me feel better for a day or less, and then I go back to how I did before.
I really get my money's worth that way...I guess...
Pro tip: Copying a Postgres database while live transactions are interacting with it frequently results in a corrupt backup.
Thankfully I test my Luanti backups.
Edit: I should clarify - My dangerous backup method was a naive file copy. I'm sure there's a different correct way to do a live backup. I just haven't checked into it yet, since stopping my Luanti server for a backup is no big deal.
Oof. This is a pet peeve of mine.
As manager, I shut this conversation down via direct messages to each team member involved.
I remind them that they agreed during retro to live with the current set of decisions for exactly two weeks until next retro.
I don't dictate much, but I do dictate that Slack isn't an acceptable place for this kind of discussion, on my team.
The only related thing, that belongs in slack, on my team, is a link to the current accepted team standard - which will be open for review and changes again during next retro.
Alternately, if there's no standard for this yet then my team knows they're encouraged to wing it until we discuss at next retro.
And yeah, I've had to open an issue to revisit a variable name after retro, lol.
My team are an opinionated bunch, and they're often perfectionists.