10

In "follow up 2" discussion the plan seemed to be that we are going to have words not code troubleshooting in the site tagline, looking about like that: Is this still the plan?


8

Since we were renamed from Programmers to Software Engineering, there was a mapping from the old domain name to the new one. But it looks like when the HTTPS rollout happened and they had to put the site's name before meta (it went from meta.softwareengineering.stackexchange.com to softwareengineering.meta.stackexchange.com), something happened with the ...


6

Great idea! Except for most of what you said! This should go on the "What types of questions should I avoid asking?" page, I don't want a new page added to the help center


5

That is apparently how Gregory House writes it. (It's not Lupus!) An examination of the symbols on the top row of the keyboard yields: Where a couple of symbols (namely the @ and the *) are conspicuously missing. Apparently Hugh Laurie never wrote them on the whiteboard during the entire series. UL is an abbreviation for a number of medical terms, ...


5

The Help Center has all the information that you need. Specifically, check out these pages: What topics can I ask about here? What types of questions should I avoid asking? How do I ask a good question? If you aren't sure if your question is on-topic or if you need help to narrow down the scope or make other improvements, you can always ask here on Meta or ...


4

Programmers Stack Exchange is a Q&A site for professionals and students in software development and related fields who are interested in getting expert answers on conceptual questions about software development. If you have a question about... software requirements software architecture and design algorithm and data structure concepts quality assurance ...


4

tl;dr People Don't Read. The phrase "How to Have Nice Things" is a reference to the phrase "This is why we can't have nice things here." The phrase is supposed to describe what happens when new people come to your community who don't understand the social norms and become disruptive. It goes something like this (example, for illustrative purposes. No ...


2

The line now reads: where to find a software library, tool, book, research paper, blog, forum, or other resources The link goes to the same meta post as before.


1

IMHO this won't change anything. People who come to "Programmers" for asking debugging questions are too ignorant to care for the site rules - they either don't read them at all, they do not understand them or they do not take them seriously. Adding more text to a rule they currently do not read or understand will not make more of those people obey the rules....


1

Objective evidence provided in the initial discussion does show that "book recommendation" Q&A's as they are now are generally sub-par and unhelpful in the long or even the short run. They tend to steer towards the "bad" end of Good subjective, Bad subjective A question of just "recommending a book on a subject" is fundamentally unclear: any subject has ...


1

I would change the question to this format: What alternatives there are for simple human readable configuration file in python? What are the pros and cons for each solution? Here is an example of a configuration file and how its handled in python. And after this copy and paste from the original question the two code blocks. The new question matches ...


1

There's nothing wrong with distilling great wisdom down into increasingly thicker, condensed concentrate. At some point, you finally lose all of the words that aren't absolutely essential to convey your point effectively and you're left with several powerful sentences that when concatenated, give users precisely what they need to 'get it' and avoid future ...


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