4 ms·
I think the previous statement that each mission spins up its own infrastructure, and that their data model encompasses a significant mix of systems points to t
by icegreentea2 7y ago
I think the previous statement that each mission spins up its own infrastructure, and that their data model encompasses a significant mix of systems points to the question not being, "should someone sitting in a cafeteria access critical resource X by default", but rather, "is it actually true that someone sitting in a cafeteria cannot access resource X1 through XN by default".
In order words, I think what they're trying to work from is that their existing systems don't present a unified or homogeneous set of interfaces or design or control. What they're trying to solve is how to fit a homogeneous interface onto their existing mess.
- lazulicurio 7y ago> the question [isn't], "should someone sitting in a cafeteria access critical resource X by default", but rather, "is it actually true that someone sitting in a cafeteria cannot access resource X1 through XN by default" I think that this is probably the main purpose of the system. The is-ought problem can become very tricky to manage with a complex network, especially if the team is on the larger size or geographically distributed.