That is one interpretation. An interpretation that, once we start thinking beyond the first concept that comes to each particular mind, ends up just as meaningl

That is one interpretation. An interpretation that, once we start thinking beyond the first concept that comes to each particular mind, ends up just as meaningless: What is a component? A global variable, a pure function, a procedure, an endpoint, a business usecase, a microservice, a microservice fleet? What is the whole, if not the same list of questions just asked in backwards order? It gets worse: Once you arbitrarily come up with one definition that you stick with in your project, does the definition you chose leave little to no room for interpretation? Do all kinds of tests that are worth writing fit neatly within those definitions? Technical terms that are so loosely defined we can do without, for only two things ultimately result from their use: Apathy, or madness.