Live data from Hacker News

StackExchange- The Stack Overflow Knowledge Exchange Platform

stackexchange.com

51–60 of 107 posts

Re: StackExchange- The Stack Overflow Knowledge Exchange Platform

#51
post #36

I think this is a great idea. My questions as a potential user would be: (1) How much visual customization will be supported? (2) I won't have to make people use OpenID, will I? (3) Does the Fog Creek/Atwood team plan more verticals that I might inadvertently find myself competing against?

#include "i love openid and so should you. here's some arguments that probably didn't convince you last time you heard them.txt"

Re: StackExchange- The Stack Overflow Knowledge Exchange Platform

#52

Seems really pricey for a relatively simple software like this. Someone write an opensource alternative? it looks like something that can be thrown together in a weekend.

A weekend? Really?

We have documented evidence in the form of podcasts that it took a team of 3 talented developers about 6 months to build StackOverflow. If you're looking for an order of magnitude estimate for how long it would take to reproduce it, that's it.

How exactly are you planning to reduce an 18 man-month project down to a single weekend of your time?

More generally, why is this attitude so common among programmers? How, in the face of documented proof to the contrary could an intelligent person like the parent still consider a site of the complexity of StackOverflow to be a "weekend job"?

Re: StackExchange- The Stack Overflow Knowledge Exchange Platform

#53
post #46
post #41

Earlier quoted context omitted.

USENET is for discussions; SO is for questions and answers. Those are orthogonal.

>Those are orthogonal. Nope.

Discussions rarely or never result in one "right" answer. Questions, on other hand, often do.

Re: StackExchange- The Stack Overflow Knowledge Exchange Platform

#54
post #16

Seems really pricey for a relatively simple software like this. Someone write an opensource alternative? it looks like something that can be thrown together in a weekend.

A lot of what makes Stack Overflow successful is the amount of effort they've put into making a great user experience. That's not the sort of thing you just come up with in a weekend. It's a continual process that requires a lot of attention. And let's face it, open source's strong point generally isn't in engineering good user experience.

When I first saw it, I liked the clean look and feel, but hated the "DAVE, I CAN'T LET YOU DO THAT" approach to permissions with regards to comments, votes, and the like. As a beginning user, you had (have? don't know if they've changed it) all these links and buttons that are displayed, but don't let you do anything; they just give you a lame message about requiring N gold stars before you can do that.

Re: StackExchange- The Stack Overflow Knowledge Exchange Platform

#55

Seems really pricey for a relatively simple software like this. Someone write an opensource alternative? it looks like something that can be thrown together in a weekend.

The price includes managed hosting. A million page views for $129 isn't bad.

Re: StackExchange- The Stack Overflow Knowledge Exchange Platform

#56

Seems really pricey for a relatively simple software like this. Someone write an opensource alternative? it looks like something that can be thrown together in a weekend.

A weekend? Really? We have documented evidence in the form of podcasts that it took a team of 3 talented developers about 6 months to build StackOverflow. If you're looking for an order of magnitude estimate for how long it would take to reproduce it, that's it. How exactly are you planning to reduce an 18 man-month project down to a single weekend of your time? More generally, why is this attitude so common among pr…

I think it's certainly longer than a weekend, but recreating something that exists is usually easier than doing it the first time. You don't really have to worry so much about how things ought to fit together - you just copy.

Re: StackExchange- The Stack Overflow Knowledge Exchange Platform

#57

I've long thought that a StackOverflow for photographers would be a great resource... but not a business. Unfortunately, the StackExchange pricing assumes that you will be a revenue-generating because no one can justify $129/month on running a free resource.

Photographers are actually a really monetizable audience compared to most. Sign up with the right affiliate program, and a single sale could cover that $129.

Re: StackExchange- The Stack Overflow Knowledge Exchange Platform

#58
post #54
post #16

Earlier quoted context omitted.

A lot of what makes Stack Overflow successful is the amount of effort they've put into making a great user experience. That's not the sort of thing you just come up with in a weekend. It's a continual process that requires a lot of attention. And let's face it, open source's strong point generally isn't in engineering good user experience.

When I first saw it, I liked the clean look and feel, but hated the "DAVE, I CAN'T LET YOU DO THAT" approach to permissions with regards to comments, votes, and the like. As a beginning user, you had (have? don't know if they've changed it) all these links and buttons that are displayed, but don't let you do anything; they just give you a lame message about requiring N gold stars before you can do that.

"Dave, I can't let you do that?" You do know that SO allows questions and answers from people without even requiring them to log in? They allow content from essentially anonymous users.

The restrictions are along the "meta" parts (voting to indicate the quality of an answer), I think it is entirely sensible to restrict these actions to users who have built up a currency of trust within the SO community.

That being said, I think you are onto to something around the user experience. Perhaps an option shouldn't be shown to someone if they cannot perform it.

Re: StackExchange- The Stack Overflow Knowledge Exchange Platform

#59

Earlier quoted context omitted.

Alright, This will be my project this coming weekend! I'll try to live up to the challenge!

No need, http://code.google.com/p/cnprog/ already exists.

What we need is an English version of CNProg.

There's a download here: http://code.google.com/p/cnprog/issues/detail?id=28

but I don't think it is production-ready yet....

Post reply on HN