Return to Answer

• http://programmers.stackexchange.com/questions/154283/should-i-demand-unit-testing-from-programmers

  Closed as "not constructive" and in my opinion rightly so - it's a discussion-oriented question designed to affirm the asker's existing belief. Discouraging questions like this one is a part of our core principles at Stack Exchange to the point where it's written down in the shared FAQ:

  To prevent your question from being flagged and possibly removed, avoid asking subjective questions where ...

  • there is no actual problem to be solved: "I’m curious if other people feel like I do."

• http://programmers.stackexchange.com/questions/154339/advice-on-scrum-for-the-solitary-developer

  Closed as a duplicate of a canonical, open question.

• http://programmers.stackexchange.com/questions/154342/are-there-references-discussing-the-use-parallel-programming-as-a-development-me

  Reference-seeking question. I don't have a strong feeling on this one. Could go either way, personally, but usually questions like this result in poorly curated lists.

• http://programmers.stackexchange.com/questions/154338/identifying-methods-with-a-specified-id-in-d

  Migrated to Stack Overflow.

• http://programmers.stackexchange.com/questions/154282/if-variable-type-not-working-properly

  Off-topic, though opted to not migrate, which is fair enough.

• http://programmers.stackexchange.com/questions/154270/is-learning-blackberry-programming-a-good-choice

  Canonically off-topic for Programmers.

• Should I demand unit-testing from programmers?

  Closed as "not constructive" and in my opinion rightly so - it's a discussion-oriented question designed to affirm the asker's existing belief. Discouraging questions like this one is a part of our core principles at Stack Exchange to the point where it's written down in the shared FAQ:

  To prevent your question from being flagged and possibly removed, avoid asking subjective questions where ...

  • there is no actual problem to be solved: "I’m curious if other people feel like I do."

• https://softwareengineering.stackexchange.com/questions/154339/advice-on-scrum-for-the-solitary-developer

  Closed as a duplicate of a canonical, open question.

• https://softwareengineering.stackexchange.com/questions/154342/are-there-references-discussing-the-use-parallel-programming-as-a-development-me

  Reference-seeking question. I don't have a strong feeling on this one. Could go either way, personally, but usually questions like this result in poorly curated lists.

• https://softwareengineering.stackexchange.com/questions/154338/identifying-methods-with-a-specified-id-in-d

  Migrated to Stack Overflow.

• https://softwareengineering.stackexchange.com/questions/154282/if-variable-type-not-working-properly

  Off-topic, though opted to not migrate, which is fair enough.

• https://softwareengineering.stackexchange.com/questions/154270/is-learning-blackberry-programming-a-good-choice

  Canonically off-topic for Programmers.

I think by now we all know how the site came about. When the new scope was handed down, it was not received terribly well and we're still sorting some of that out. The fact is, though, that throughout most of last year, the site slowly evolved to move away from the "Stack Overflow's toilet bowl" image and to what it is today. It happened through comments, (sometimes bitter) meta arguments, flag handling, etc., and look at what we have now - there's an engaged, active community involved in moderation and governance. Even though there were a couple discussions, the site name did not matter.

I think by now we all know how the site came about. When the new scope was handed down, it was not received terribly well and we're still sorting some of that out. The fact is, though, that throughout most of last year, the site slowly evolved to move away from the "Stack Overflow's toilet bowl" image and to what it is today. It happened through comments, (sometimes bitter) meta arguments, flag handling, etc., and look at what we have now - there's an engaged, active community involved in moderation and governance. Even though there were a couple discussions, the site name did not matter.