Noah Gift wrote:
Bob Jake wrote:Curious to see the definition of Pragmatic here. Is this pragmatic process or pragmatic 'bias' results ?
The process is pragmatic here. The general problem I have seen both an engineering manager and a professor is a lack of "bias for action" to use a phrase they use at Amazon. How can an individual or organization get past the theoretical and get into solving a solution an efficient and effective way. For example, maybe using a high level tool like AWS Sagemaker to deploy a machine learning model could be called pragmatic vs rolling your own ML model into production and deploying into manually orchestrated web services.
Originally posted by Marc Peabody:
The only major negative consequence I can see with this approach is that potential service clients who discover a service endpoint see the types defined in the request or response and assume that all of these "optional" elements are relevant to the endpoint.
What about just forgetting harmonization altogether? I imagine it would be tremendously frustrating for a client to call two difference services with similar data but in one service a tag is organization while in the other service it is organisation or org or company. It would be terrific to at least keep tag names in harmony.