[jlogic77]

Is it going to be better than just putting the code in a search engine like google or something. Most of the codes I come across are unique enough that I get a direct match pretty quickly. Also what helps me is seeing related forum posts and other comments on resolving the issue, the definition in on itself is often useless.

[ericb]

I have nothing to do with the site or author, but I can suggest the following:

-Google defaults to under-emphasizing results related to errors specific in newer versions of software. So when a bug in a new release comes out, info is often no where to be seen--it is obscured by older items with higher rank.

-Google includes links to both questions, and answers. I only want answers.

-Google's results are across multiple pages and obscured in forum discussions. I want one page with all the answers and info.

-Google frequently returns results from experts exchange, which involves scrolling to the bottom. Additionally, I've talked to developers who don't even realize the unobscured answer is at the bottom.

-Some code queries do not translate well into regular searches because the characters have meaning. Off the top of my head example: select * from blah

-There is not always a nice centralized place to go to share it with the world know when you have a fix.

That said, I'm not sure this site implements solutions to all these problems, but a wiki-type site could. Isn't Jeff Atwood doing something with a similar idea?

[okeumeni]

Depending on the system your working on finding a fix or explanation to an error is not always easy. The next step is to allow users to post alternative fix to errors or link to forum where research can be extended.