Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Meta

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Post History

80%
+6 −0
Meta Asking software architecture related questions on Software Development community

Personally, I'd say that it depends on the question. Over on that other site, this ban was instituted to avoid opinion-based questions. For instance, suppose you asked: Is Angular a great framewor...

posted 3y ago by meriton‭

Answer
#1: Initial revision by user avatar meriton‭ · 2020-08-24T23:04:27Z (over 3 years ago)
Personally, I'd say that it depends on the question. 

Over on that other site, this ban was instituted to avoid opinion-based questions. For instance, suppose you asked:

> Is Angular a great framework?

and received the following replies:

> Absolutely, i really love it!

> No, I hate it!!!

Would that be helpful to you or future visitors? If answers simply voice an opinion without giving any evidence why that opinion is correct, it boils down to a simple popularity contest rather than communicating any knowledge. 

That is, I think it is ok to ask for opinions, as long as you also ask for the evidence or rationale that backs them up. Asking about pros and cons is good start for that.

In addition, you might narrow the question further to avoid wall of text issues, and make answers more generally applicable to future visitors. 

For instance, in the linked question, I'd have happily answered whether replicating the DB is better than sharing a DB from a security perspective, but that aspect alone, if backed up by proper reasoning and arguments, is likely to result in quite a substantial answer. But "how to adapt the architecture" is a very broad question I could not possibly do justice to within the space and time constraints of a Codidact answer (even if I had all the requirement documents I would need to assess your application's needs).

Therefore, narrowing the question to the particular aspect you are interested in is even more crucial (and possibly more difficult) for architecture questions than for code questions.

All that said, I think a blanket ban would kill many good and valuable questions along with the bad, and declaring such an important subject taboo would leave significant gaps in the knowledge of our visitors. But we should take extra care to ask answerable questions, and take the time to back up our opinions with reasoning and facts.