News for hackers. Stuff that matters.
Re:The Honest Troubleshooting Code of Conduct by mcguire on Sunday May 02, 2021 @06:39PM (#27019696)
Thank you!

I was mildly troubled by the comment towards the end, "There were third- and fourth-generation members who I had no idea about who had signed up to talk about reliability without being second-guessed to death and hounded by people who just wanted to talk about [...] "a lot of work went into that"."

I've been sensitized, I guess. Yes, the way we do things is probably stupid. Yes, your favorite new framework or method or language or whatever might trivially fix all the problems that you can see. Heck, you might even be the smartest person in the room. But, there might also be a reason things things are stuck at a historical, local maximum.

Re:The Honest Troubleshooting Code of Conduct by Kalium on Sunday May 02, 2021 @07:00PM (#27019867)
You are absolutely right, and I think the author would agree with you. Sometimes there are strong, compelling reasons that justify not changing things.

Inconveniently, sometimes the reason is "a lot of work went into that".

Re:The Honest Troubleshooting Code of Conduct by cratermoon on Sunday May 02, 2021 @10:12PM (#27020946)
Chesterton’s Fence: don’t ever take down a fence until you know why it was put up