Ways to improve LessWrong

Adam Zerner

I think it'd be a good idea to keep a list of the ways we'd like to see LessWrong improve, sorted by popularity. Ie. email alerts for new responses.

So if you have an idea for how LessWrong could be better, post it in the comments. As people up/downvote, we'll get a sense for what the consensus opinions are.

I think there's a pretty good amount to be gained by improving LessWrong.

I think there's a lot of low-hanging fruit (like email alerts for new responses).
Conversations here are actually useful and productive. Facilitating conversation should thus lead to more of these useful and productive conversations (as opposed to leading to more of an unproductive type of conversation). (Sorry, I didn't word this well; hopefully you guys know what I mean.)
Perhaps something big would come out of this list (like meet-ups). Perhaps rationality hack-a-thons (whatever that means)?

I'm not a good enough coder now, but once I am, I think I'd like to do what I can to make LessWrong better. I'm starting a coding bootcamp (Fullstack Academy) on Monday. By the end of it, I should at least be competent.

Note: I say "ways to improve" instead of "features" because "ways to improve" is more general.

I think it'd be a good idea to keep a list of the ways we'd like to see LessWrong improve, sorted by popularity. Ie. email alerts for new responses.

So if you have an idea for how LessWrong could be better, post it in the comments. As people up/downvote, we'll get a sense for what the consensus opinions are.

I think there's a pretty good amount to be gained by improving LessWrong.

I think there's a lot of low-hanging fruit (like email alerts for new responses).
Conversations here are actually useful and productive. Facilitating conversation should thus lead to more of these useful and productive conversations (as opposed to leading to more of an unproductive type of conversation). (Sorry, I didn't word this well; hopefully you guys know what I mean.)
Perhaps something big would come out of this list (like meet-ups). Perhaps rationality hack-a-thons (whatever that means)?

Note: I say "ways to improve" instead of "features" because "ways to improve" is more general.

Ahh, I see.

Regarding cost of implementation, 1) I'll probably be willing to work on it and 2) I sense that the benefits far outweigh the costs, and that we'll be able to get people to work on it. Especially if it's well thought out and some nice mockups are made that are convincing.

Regarding the owners of LW being reluctant to change, I don't know much about this issue so it's tough to say, but I sense that 1) if we get enough community support, they'll be pretty likely to go along with it and 2) I would think that they're smart enough to see the benefits would be large and if volunteers like me (and you?) would be willing to work on it, the costs could be pretty small.

Consider the fact that many, many programmers frequent LW. It's quite likely the majority of members know how to program a computer, and most of them have a very high level of skill. Despite this, contributions to LW's codebase have been minimal over the life of this website. I take this as extremely strong evidence that the friction to getting any change through is very, very high.

9

Ways to improve LessWrong

9

9

9

Ways to improve LessWrong

9

9