3 ms·
This feels like another scrum workshop or whatever they teach to non tech managers. Forcing a specific workflow without ever explaining why (context -> containe
by SPBS 4y ago
This feels like another scrum workshop or whatever they teach to non tech managers. Forcing a specific workflow without ever explaining why (context -> containers -> components -> code), not a single mention about the problem domain but just a generic framework you are expected to fit all problem domains into. You learn more about the framework before you learn about the problem. Example:
"Here's a container! It is either a Server-side web application, Client-side web application, Client-side desktop application, Mobile app, etc etc". Okay why? Why are you making this distinction? Why not just call it a web server, a web app, a mobile app? What could this concept of 'container' be so useful that you have to invent it and make everyone internalize it? Does it contribute to the discussion? Are you trying to arbitrarily force labels onto things so you can use the same lingo to talk about every problem?
- deleted 4y ago[deleted]
- captaincaveman 4y agoIt's called abstraction, which is used when modelling categories of things, you do it lots when you write code right, so things are reusable. Like you probably have something called an iterrable in your programming language of choice, so why not just call it a linked list, or a vector, is basically the argument you're making in my opinion. To be fair, I do find some modelling languages do disappear into too much abstraction, they basically end up like being a Upper Ontology [1] and lack instances/examples that make them approachable in practice. [1] https://en.wikipedia.org/wiki/Upper_ontology https://en.wikipedia.org/wiki/Upper_ontology