4 ms·
> > You basically asked how to architecture a security aspect of your software. And you asked for other people's experiences to boot, instead of a canonical sol
by Izkata 9y ago
> > You basically asked how to architecture a security aspect of your software. And you asked for other people's experiences to boot, instead of a canonical solution.
> That's exactly what I want to discuss on SO.
Broad-ish architecturing questions belong on https://softwareengineering.stackexchange.com/ https://softwareengineering.stackexchange.com/ (formerly known as programmers.SE). A good rule of thumb for which of those two sites to go to is, does your question have code?
(Also, "discuss" is a forbidden word on StackExchange - it's Q&A, not discussion)
- vadimberman 9y agoI wonder how many people can pinpoint where the boundary between the two communities lies. What does this division help to achieve? The two communities are in exactly the same format.
- shagie 9y agoThe distinction between the two is described in the help/on-topic page ( https://softwareengineering.stackexchange.com/help/on-topic https://softwareengineering.stackexchange.com/help/on-topic - be sure to follow the links) and various faq tagged pages on the meta - https://softwareengineering.meta.stackexchange.com/q/6483 https://softwareengineering.meta.stackexchange.com/q/6483 The division is there so that questions about design and architecture have a place to get asked that don't get closed as off topic (lacking code) on Stack Overflow. Consider a question like In an agile process, how much work should be done by the PO on a project or feature before presenting it to the team? - https://softwareengineering.stackexchange.com/questions/367694/ https://softwareengineering.stackexchange.com/questions/3676... The format doesn't dictate topicality... there are many sites that use the same format. https://cooking.stackexchange.com https://cooking.stackexchange.com for example.