StackOverflow.com : the new venture from Joel Spolsky
joelonsoftware.com
joelonsoftware.com
Scenario: I'm compiling something on Leopard and it stops with an error. I type the command "wtf"
ERROR: compile quit because of this reason xxxxxxxxxx
> wtf
It automatically records the output of the error and saves it some web site's database. It can find others with the problem and open a browser to the discussion on that issue. Someone else probably already found a way around it or there's some library i'm missing and someone there has explained what it is.
The 'wtf' command would automatically do that "google search" for me and log my info to help others.
Our long-term plan is to integrate all over the place in software. For example, we have a proof of concept for this we announced at PyCon that does what you're describing inside the Python interactive interpreter: http://blog.bug.gd/2008/03/29/error_help-for-python-hackers/
While we're excited from a business perspective for integrating into company's GUI apps, as hackers we're very excited about the potential here for completely changing the dynamic of the open source community.
Imagine if every new user, casual hacker, etc., trying out a new open source tool, could immediately get assistance whenever they ran into an error message. What may have taken 6 hours to get configured (and maybe stopped them) could now be a step-by-step "ah-ha" process for common scenarios.
That's precisely what we want to enable. In addition, most of the open source community doesn't even get very good feedback on how many people run into particular errors and give up entirely. This tool would give them the ability to see that, track errors, and put in their own solutions for when they find out people are running into those.
We have a lot of cool plans for this, and I absolutely love to read other people interested in this same endeavor. We're very keen on hearing more feedback on this.
Is this inspired at all by what Fred Brooks talks about in the Mythical man Month, where each run of a program had to be recorded, and was public within the project?
No hiding your bugs there...!
I wouldn't mind seeing a One True Site for technology questions again and sure hope this becomes one.
I certainly would not mind reading this site in a newsreader.
So, I think the problem isn't that web forums are bad, merely that the interface for using them isn't as good as a newsreader. Might be a good opportunity...
That said, the fact that they tend to have a government of sorts, can be a big advantage. A forum can potentially do away with trolls and encourage intelligent conversation in a way the Usenet cannot.
That's our service: http://bug.gd
Our services focus solely on error messages-- the goal is to make it so no one ever has to solve any error message someone already bypassed.
While we're a solution database, it's not quite the forum as Joel's site sounds like it will be (more like Experts Exchange).
We use error messages as a vector for connecting users with different solutions. This let's us get a little more exact on the possible solutions, but we wouldn't cover typical programing or sysadmin tips/tricks. For example, we're also a Firefox extension, a Python interactive interpreter plugin, and will eventually grow to capture error messages for all sorts of software and help people right away while they use the applications.
(edit: admittedly this is still speculative)
Random example: http://www.experts-exchange.com/Database/Oracle/Q_22765568.h...
I know I'll attempt to contribute
Yet they want to build a giant sink of answers for technical problems. That sink already exists, it's called Internet: post an answer to any question on millions of message boards, google groups ans sites like news.yc. Internet has has an awesome search facility built-in - people will find what you said.
Search for this on google: "The author of this, David Beazley" and you'll get news.yc page with someone's comment containing those words only 4 (!) hours ago (from this moment as I'm writing this).
Why another site? Sure, they have the blogging powers to hype the hell out of their project, but come on...
(ha - totally unintentional switch from first names to last names)
Joel Spolsky and Jeff Atwood are two of my most respected programming heroes.
here's to hoping. i'd love to see a consolidated resource.