How should we handle overlap with Stack Overflow? Unlike SU, where there is almost no overlap there is quite a bit of overlap between GIS and software devlopment. Both in terms of questions which already exist there and in terms of what logically falls into each domain. For example if I create an arcgis model, export to a script, and then start working on that I'm not really "developing" in the SO sense, but development knowledge is involved.
I'm already finding this overlap pretty frustrating though: I answer a lot of questions on the StackOverflow geolocation tag, and now sometimes they get re-posted over here and I'm not sure if my answer at SO will now simply go to waste or if I need to repeat my answers at gis. It also seems pretty frustrating for questioners who have to repeat their question and then monitor two locations for answers.
Are software developers just supposed to keep in the back of their heads a list of every StackExchange site so that when they're about to post a question that might be related to topic X on StackOverflow they instead switch to a new domain? I think ideally questions could be shared between sites (via a special tag, say); if not, then I think the community needs a lot of documentation (and documentation that appears just in time) on both sites about which questions go where.
I don't know if this is related, but this url: https://stackoverflow.com/questions/tagged/arcobjects
There are no Featured questions in the arcobjects tag at the moment. Perhaps you'd like to select a different tab (sic)?
Note that there are indeed questions in SO with the arcobjects tag.
Is this part of an effort to encourage users to move to https://gis.stackexchange.com/questions/tagged/arcobjects ?
If so, maybe the message could be a bit more informative.
Update: I realize now I had earlier navigated to "featured" questions before browsing to the arcobjects tag, so there is no bug. Still I wonder if SO could inform users about GIS.stackexchange.com when they choose certain tags, then migration could be encouraged. Certainly other stackexchange sites face a similar issue.