Live data from Hacker News

Show HN: Realtime Coding Q&A. Stack Overflow meets IRC

enginehere.com

21–24 of 24 posts

Re: Show HN: Realtime Coding Q&A. Stack Overflow meets IRC

#21
This concept is really neat not to mention useful. It is sometimes annoying the post on traditional forums like SO and have to wait for a response you may never receive. This makes getting help seem a lot more direct and immediate. Its sort of like E-mail and Instant messaging. SO would be like Email, still useful of course, and EngineHere is the instant messaging platform for a more dynamic/instant environment..

Re: Show HN: Realtime Coding Q&A. Stack Overflow meets IRC

#22
post #21

This concept is really neat not to mention useful. It is sometimes annoying the post on traditional forums like SO and have to wait for a response you may never receive. This makes getting help seem a lot more direct and immediate. Its sort of like E-mail and Instant messaging. SO would be like Email, still useful of course, and EngineHere is the instant messaging platform for a more dynamic/instant environment..

That was the goal. As I've built it, I've been actually posting the bitly links to my issue pages on Stack Overflow, IRC, and elsewhere. I set desktop notifications for myself and go about my work until someone hits one of my pages (I then start a chat)

Re: Show HN: Realtime Coding Q&A. Stack Overflow meets IRC

#23
post #5

As a fairly high-output Stack Overflow contributor, this is quite interesting. It seems to say "Stack Overflow is too slow, we need something faster". I tend to think (I'm biased, of course) that SO already is rather fast; i.e. that most questions (in tags I care about) get answered rather quickly. Not only because of me, of course! I'm just a small part of the machinery. So, what's the next step, a service where I c…

> registered as a helper and have a computer call me

Not sure if serious, or already registered with Google Helpouts...

Re: Show HN: Realtime Coding Q&A. Stack Overflow meets IRC

#24
This concept could be monetized quickly and perhaps in a big way if you can saas it to web apps whose users need help in real time, but have to use the old "support ticket" mechanisms and wait and hope that their ticket gets answered quickly.

If you package your technology such that it can be embedded into any web app that has this problem, the web app could then leverage its users (its customers) to help each other out in real time.

Just a thought :-)

Post reply on HN