4 ms·
They have tried to split out the Software Engineering Stack Exchange site for this per the reply at https://meta.stackexchange.com/questions/124867/where-should
by zerkten 4y ago
They have tried to split out the Software Engineering Stack Exchange site for this per the reply at https://meta.stackexchange.com/questions/124867/where-should-i-ask-software-architecture-design-questions https://meta.stackexchange.com/questions/124867/where-should.... As you note, these discussions are more complex than just a question and answer.
I'm curious how often you find that people get actionable information from outside that they couldn't have discovered with better introspection or understanding of the basics. I'm in a similar role and find that people want validation of working systems due to some new person casting shade, have a desire for more exotic technology, or just want people to shoot the breeze with peers on these topics. The answers to their actual problems are often staring them in the face, but are too mundane or boring to accept. Given the pressure to deliver, they'd be better off focusing on the basics for their stakeholders which is the place I try to get them to.
- mattbrewsbytes 4y agoI think a rational discussion of an architecture issue shouldn't discuss specific programming languages/frameworks or options of exotic tech. It should be at a much higher level because those things mostly aren't relevant. If the discussion leads to "XYZ message thing behaves this way, how do you ..." that is more of an implementation/programming discussion and not architecture.