• 0 Posts
  • 756 Comments
Joined 4 个月前
cake
Cake day: 2026年2月22日

help-circle












  • If we switch the argument to being about diverting a watercourse, or regrading land, it suddenly falls apart because it becomes clear that these things do not exist for intelligent reasons.

    This is not a compelling analogy. Many things in nature may not exist for an intelligent reason, but their presence matters in ways that may not be obvious. Diverting a waterway may cause tremendous damage to the ecosystem and other downstream (pun intended) things. That is an excellent example of why you should understand the current system before attempting to change it.

    I don’t think it’s a bad idea to try and understand the world or to mitigate risks when making changes. I think chesterton’s fence is a shite argument because it implies that everything which exists has a planned purpose and favours the status quo which may be intoler

    I don’t think the implied plan purpose is necessary for the argument to make sense. The point of the story is it’s not always clear what things are load bearing, nor what loads they bear.

    If the chesteron origin is distracting to you, let’s discard it. I think we agree that changing a complex system without attempting to understand it first is foolish.






  • What is an example of a safety rule who’s conditions no longer exist which would not have the conditions almost immediately return if the rule was removed?

    My job is populated by dinosaurs that only recently adopted git for version control. They had some rules and procedures that made a kind of sense when deployment meant “I’ll scp the files to the prod server”, but don’t add value anymore.

    Some people had a rule where after “deploy” they would SSH into prod and check the md5 hash of the files and compare them to their local copy. You don’t have to do that.

    They also wanted to only allow one person to work on a file at the same time because “you can overwrite their changes”. Git handles that fine (unless you really fuck up the merge conflict, admittedly)


  • Sometimes the real reason is uncomfortable and they don’t want to say it out loud. Like, “the CEO is an idiot, and wants it this way for stupid reasons”

    Though maybe “the CEO doesn’t understand how Google calendar works, so he thinks putting our time off in a shared spreadsheet is easier” would satisfy?

    At my job a lot of stupid things come out of “someone high ranking doesn’t understand computers” or “they don’t benefit from fixing this, so it’s easier for them to leave it stupid”