It seems like there’s a consistent disagreement here about how much implementation details matter.
And I think it’s useful to remember that things _are_ just implementation details. Sometimes you’re burning coal to produce energy, and if you wrap up your entire thought process around “coal is necessary to produce energy” you might not consider wind or nuclear power.
But realistically I think implementation details do matter, and if the best way to get X is with Y… no, that shouldn’t lead you to think Y is good in-and-of-itself, but it should affect your model of how everything fits together.
Understanding the mechanics of how the world works is how you improve how the world works. If you abstract away all the lower level details you lose the ability to reconfigure them.
I don’t disagree with what you say, but I’m not sure that it’s responsive to my comments. I never said, after all, that implementation details “don’t matter”, in some absolute sense—only (here) that they don’t matter as far as evaluation of outcomes goes! (Did you miss the first footnote of the grandparent comment…?)
Understanding the mechanics of how the world works is how you improve how the world works. If you abstract away all the lower level details you lose the ability to reconfigure them.
Yes, of course. But I am not the one doing any reconfiguring of, say, CFAR, nor am I interested in doing so! It is of course right and proper that CFAR employees (and/or anyone else in a position to, and with a motivation to, improve or modify CFAR’s affairs) understand the implementation details of how CFAR does the things they do. But what is that to me? Of academic or general interest—yes, of course. But for the purpose of evaluation…?
It seemed like it mattered with regard to the original context of this discussion, where the thing I was asking was “what would LW output if it were going well, according to you?” (I realize this question perhaps unfairly implies you cared about my particular frame in which I asked the question)
If LessWrong’s job was to produce energy, and we did it by burning coal, pollution and other downsides might be a cost that we weigh, but if we thought about “how would we tell things had gone well in another 20 years?”, unless we had a plan for switching the entire plant over to solar panels, we should probably expect roughly similar levels of whatever the costs were (maybe with some reduction based on efficiency), rather than those downsides disappearing into the mists of time.
(I realize this question perhaps unfairly implies you cared about my particular frame in which I asked the question)
Sure, but more importantly, what you asked was this:
In 20 years if everything on LW went exactly the way you think is ideal, what are the good things that would have happened along the way, and how would we know that we made the right call?
[emphasis mine]
Producing energy by burning coal is hardly ideal. As you say upthread, it’s well and good to be realistic about what can be accomplished and how it can be accomplished, but we shouldn’t lose track of what our goals (i.e., our ideals) actually are.
I’m not too worried about the conversation continuing in the manner is has, but I’m pretty sure I’ve now covered everything I had to say before actually drilling down into the details.
It seems like there’s a consistent disagreement here about how much implementation details matter.
And I think it’s useful to remember that things _are_ just implementation details. Sometimes you’re burning coal to produce energy, and if you wrap up your entire thought process around “coal is necessary to produce energy” you might not consider wind or nuclear power.
But realistically I think implementation details do matter, and if the best way to get X is with Y… no, that shouldn’t lead you to think Y is good in-and-of-itself, but it should affect your model of how everything fits together.
Understanding the mechanics of how the world works is how you improve how the world works. If you abstract away all the lower level details you lose the ability to reconfigure them.
I don’t disagree with what you say, but I’m not sure that it’s responsive to my comments. I never said, after all, that implementation details “don’t matter”, in some absolute sense—only (here) that they don’t matter as far as evaluation of outcomes goes! (Did you miss the first footnote of the grandparent comment…?)
Yes, of course. But I am not the one doing any reconfiguring of, say, CFAR, nor am I interested in doing so! It is of course right and proper that CFAR employees (and/or anyone else in a position to, and with a motivation to, improve or modify CFAR’s affairs) understand the implementation details of how CFAR does the things they do. But what is that to me? Of academic or general interest—yes, of course. But for the purpose of evaluation…?
It seemed like it mattered with regard to the original context of this discussion, where the thing I was asking was “what would LW output if it were going well, according to you?” (I realize this question perhaps unfairly implies you cared about my particular frame in which I asked the question)
If LessWrong’s job was to produce energy, and we did it by burning coal, pollution and other downsides might be a cost that we weigh, but if we thought about “how would we tell things had gone well in another 20 years?”, unless we had a plan for switching the entire plant over to solar panels, we should probably expect roughly similar levels of whatever the costs were (maybe with some reduction based on efficiency), rather than those downsides disappearing into the mists of time.
[edit: mild update to first paragraph]
Sure, but more importantly, what you asked was this:
[emphasis mine]
Producing energy by burning coal is hardly ideal. As you say upthread, it’s well and good to be realistic about what can be accomplished and how it can be accomplished, but we shouldn’t lose track of what our goals (i.e., our ideals) actually are.
Okay, coolio.
I’m not too worried about the conversation continuing in the manner is has, but I’m pretty sure I’ve now covered everything I had to say before actually drilling down into the details.