Hi Zac,
These are some great points!
On Tue, Dec 29, 2009 at 1:01 PM, Zac Bowling wrote:
> Basic questions get answered usually here just as long as they are not
> obvious questions on the Wiki. :-)
That doesn't really mean they shouldn't be answered at all. If new
members of the community are
Basic questions get answered usually here just as long as they are not
obvious questions on the Wiki. :-)
Stack Overflow has a lot of overflow (no pun) with other development
communities. You see a lot of questions around how to use the twitter API
with specific languages or frameworks on Stack Ov
Hi Ken, Andrew,
Thank you for your thoughts! I had considered a Stack Exchange and
have set up a couple of experimental Q&A communities using it. After
the seeing what the Android and Adbobe teams are doing I think it
makes much more sense to keep the programming discussion in one place
on and av
> It seems like creating a stackexchange would just split the support power.
+1, totally.
>
One issue I've noticed with Stackoverflow is it is harder for new
developers to participate where as the barrier for entry on Google
Groups is just having an email address.
Some email groups
can be ver
It seems like creating a stackexchange would just split the support power.
Better to just push people to the Stackoverflow tag.
Just noticed that Adobe is also using Stackoverflow for official support.
One issue I've noticed with Stackoverflow is it is harder for new developers
to participate whe
Jonathan,
Good points and initiative.
>
> I do not believe Twitter have the resources to recreate the success of
> Stack Overflow for Q&A purposes.
Have you considered setting up a Twitter Dev Q&A beta site on
stackexchange.com? I have, and someone probably could, but I thought I'd wait
and
