Hot answers tagged

149

Software Engineering. I think it's as good a site title as you're going to get. Here's why: It's not "Programmers," which smacks of people who write teh codez. Electrical Engineering's name change (from Electronics) was very good for them. It raised the quality bar on that site significantly. The On-Topic page, Tour Page, or Whatever New Users See First™...


98

This answer is to summarize the requests for Stack Exchange in a single post. It is a community wiki, so if something else seems to be a consensus in this thread, feel free to add or edit it. Name Change to Software Engineering Tour / Tag Line Welcome Software Engineering is a question and answer site for people involved in the Systems Development Life ...


47

Do you care about applying craftsmanship1 or engineering to the planning, design, development, testing, deployment, and maintenance of software? Are you concerned with all aspects of software development (and not just writing/debugging/testing code)? Are you concerned with the practice (as opposed to the theory) of software development? If you can answer "...


42

How happy I am that this day has finally come! These are my suggestions, some similarities to Snowman's answer with certain omissions and value-adds. Site Name I favor the new site name, Software Engineering I am neutral to the new site name, Software Development I dislike the name, Software Architecture however as this can be considered a distinct subtype ...


34

Why is "Programmers" changing to "Software Engineering?" Because the name "Programmers" invites all sorts of questions that are only vaguely related to software engineering, questions that we don't want. Has anything else changed? Yes. The Tour and the Help Center have a new tag line, the public description of the site which is ...


31

Frankly, I think that you are off base. Or at least your "change enforcement" is too thinly scoped. No amount of name changing or scope massaging or helpful blurbs will fix the community. As it stands, we have a fairly insular group of regulars who view questions as something to vet - things to protect the site from. We reliably have purges where old, ...


30

Thus, questions that are not answerable -- discussions, debates, opinions -- should be closed as subjective. By and large this is true, but do you ever stop long enough to consider if there is actually some pretty good content behind a long-standing question — content that didn't become a never-ending list of answers or break down into a needless, ...


28

Ask us about your specific problem. Focus your questions on a specific, design-related problem you are having. Instead of asking "Is this SOLID," show us part of your project, tell us why you think it's not SOLID, and ask us how you can make it more SOLID. State your criteria. Questions asking if something is a "best practice," without ...


22

I think we should not change the scope at all. There is no reason the sites (Law and Open Source) can't have overlapping scope with Progs. For example questions about algorithms are on topic both here and Stack Overflow. I really don't see any reason for us to change our scope based on what other Stacks are or are not doing. We should want the questions we ...


21

Yes We currently have lots of great Q&A's that specifically address licensing. Questions about software licences are well within the purview of the Software Development Life-Cycle. We should not be gerrymandering our site's scope to specifically exclude them just because Law.SE exists. Instead, we should be jealous of our questions. If an aspect of ...


17

I Love It In short, our scope does in fact have a few small edge cases that are well established but relatively uncommon (Eg. software license questions from the perspective of a software engineer, some overlap with Project Management) however is it terribly important that we complicate and confuse? This is the problem when the community is a group of ...


16

I like maple_shaft's answer, however wanted to write my own for reducing the on-topic page's wall-of-text since it's far too long for a comment on his answer. What topics can I ask about here? Software Engineering Stack Exchange is a Q&A site for professionals and students in software engineering and related fields who are interested in getting ...


16

No The concept of licensing questions being on-topic has a long history. When the topicality of this site was first discussed, "software law" was originally on-topic. But this definition of legal questions needed clarification. Eventually, we even updated the help documentation to better reflect scope. And then had to make more changes to the FAQ (which pre-...


15

Here are my thoughts on the solutions currently listed. Change Name is BAD because it was already rejected by SE top brass and for seemingly valid reasons; namely, there isn't an alternative name that narrows the definition whilst staying true to this site's purpose. Add Sub-title is GOOD providing that the right wording could be found. Sub-titles are less ...


14

Something came up in the comments on Robert's answer that I'd like to address... But why should it remain open? Curation of existing content for questions that are off topic, primarily opinion, or too broad is most easily done when the question is closed. -- MichaelT Closure doesn't mean deletion, and I think many community participants confuse the two. ...


12

The motivation behind the rebranding is not to change the focus of the site and express this through the title. It is to make the title match the actual focus more closer, as it is understood by the experts of this community during the last 2-4 years. So if you had a question valid for "Programmers" in that time period, it will most probably still be valid ...


11

Site Name I've started to come around to the name "Software Engineering". Although I still have some lingering objections regarding the overuse of the term "engineering" in software development, I think that the benefits would outweigh my personal objections. It does bring to mind a professional-oriented site that caters to people that work throughout the ...


10

(special edition for folks coming from Math.SE, reposted from Math meta - screen shot / 10K link) Hint: Software Engineering Stack Exchange doesn't do coding help and expect research before asking Sometimes, we at Software Engineering get a stream of troublesome questions from folks with linked accounts at Math.SE. One of them was kind enough to explain why ...


10

Redirecting the Question The sites rules for posting questions support and direct the site towards its stated aims I don't think there can be disagreement that the current posting rules accurately direct questions towards this site's intent; so the question ceases to be 'are the posting rules incorrect or excessively restrictive' but rather becomes 'Is the ...


10

I am a software engineer. I use StackOverflow to solve my daily problems. I am surprised so many are in favor of renaming to Software Engineering, as I can only see it leading to confusion. I come here to learn software design, but taking a glance at the questions I can see there is more: workplace issues, software best practices, coding techniques, ...


10

No. Software Engineering is a site for asking questions directly related to the Systems Development Life Cycle (but not code troubleshooting or writing specific code). Questions seeking career or education advice are off topic. They are only meaningful to the asker and do not generate lasting value for the broader programming community. Furthermore, in most ...


9

No, Programmers should not make questions about open source licensing off-topic. There is a subset (that we must define in a clear way) of questions that are on-topic on both Programmers and Open Source. However, we should update our Help Center to link to Open Source, Law, and Software Recommendation (specifically their /help/on-topic pages) to help ...


9

Allow me to introduce myself, I'm Zizouz212, and I'm a moderator over at Open Source. I might as well recap what we cover as site scope: Anything libre/open-source/creative-commons licensing Anything to do with open-source project management Any questions that ask the community to recommend a license for a project - We allow anything that is in the esteem ...


Only top voted, non community-wiki answers of a minimum length are eligible