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™...
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.
Change to Software Engineering
Tour / Tag Line
Software Engineering is a question and answer site for people involved in the Systems Development Life ...
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.
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 ...
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 ...
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 ...
I think that, generally, design review type questions are on-topic. However, the problem is how broad they are. My concern for this type of question is that most of them may be more suited to a discussion environment. I do think that there are good design review questions, but they need to be clear and specific and not soliciting general feedback. ...
As a rule of thumb, questions are on topic if they are answerable by expert programmers, as opposed to expert lawyers.
Additionally, here are some questions you can ask yourself to determine if your question is on topic or not:
Is the question about the spirit of the license, or the detailed terms of the license?
Programmers can easily understand things ...
Well, I am with you here, Robert, but not just for the reason you gave. The whole description is
too damn long
it is not surprising people read only the first half of it and forget about the second half.
Here is the full text:
Q&A for professionals, academics, and students working within the systems development life cycle who care about creating, ...
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 ...
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-...
The difference between the two sites is the difference between computer science and software engineering.
Programmers is focused on the practical aspects of building software - requirements, architecture, design, testing, deployment, configuration management, software quality, process and project management. Things of unique interest to software engineers ...
My understanding on legal/licensing questions has always been: If it can be reasonably and confidently answered by an experienced programmer, without needing to consult any actual lawyers, then it's okay here.
For instance, it's fair to ask a programmer whether or not you can legally sell a closed-source program that dynamically links to a GPL'd library. ...
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 ...
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, ...
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 ...
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 ...
This is where the diagram on the Help Center comes into play.
Generally the accepted definition of what is acceptable here, whether it be career advice or not, is within the blue area of the diagram below.
I am having trouble convincing senior members of the team to go into crunch mode, how can I deal with senior members that are not willing to work 60+ ...
I prefer to use "and-clause" borrowed and slightly rephrased from Codereview.SE
Does my question contain design? (Please include the design in the question, not a link to it)
Did I write that design?
Is it actual design from a project rather than pseudo-design or example design?
Do I want the design to be good design, (i.e. not design-golfing, ...
Generally speaking if the question has a definite answer and is not-implementation dependent, we'll take it. Example:
Which hashing algorithm is best for uniqueness and speed?
This question has a definite answer and is in no way implementation dependent. The top answer is a work of art as well as being good solid science. This is the standard that we ...
Career advice is off-topic, as mentioned in the Help Center. It's also one of the off-topic close reasons. Such questions are too unique to your particular situation to be useful to the broader audience of software development professionals.
Upon skimming your headers to see if they would apply to my questions, my first instinct was to think wait some of those are actually on-topic! until I read your detailed notes. Perhaps we could clarify some of the header areas?
Review my design
We don't review entire software designs; that's a discussion, not a question. If you have a specific ...
Questions that merely ask "What is the best way to do something" are not answerable. Because there are always several ways to solve a problem in computing, there is no "best" way; there is only the way that most effectively solves your specific problem, in whatever way you define "effective."
So instead of asking what is the best way, tell us what "best" ...
We have explicit guidance for design review questions. However, if you're asking about Turing Machines in the theoretical computer science sense, you may want to ask on Computer Science (check out their Help Center and Meta first, though). We tend to focus on building software systems, while Turing Machines are models of computation.