4 ms·
Sometimes, an analogy is just an analogy (and not a model). They both have their uses, but if you are taking an analogy to be a model, you are likely to wander
by mannykannot 9y ago
Sometimes, an analogy is just an analogy (and not a model). They both have their uses, but if you are taking an analogy to be a model, you are likely to wander into areas of inapplicability. In particular, you cannot validate a claim about software simply on the grounds that it is so in the physics analogy.
- wenc 9y agoThat is true. In many countries, there have been efforts to create a "software engineering" profession, mostly motivated by the desire to elevate software development to the level of a profession, with the attendant standards, professional accountability and governing body. However, this has been fraught with problems, because software engineering differs from physical engineering in fundamental ways and many people have realized that applying physical engineering principles to software leads one to commit an fundamental error in paradigm. At a basic level, software is a procedural epistemology that manipulates ideas that do not necessarily have to correspond to physical objects. It doesn't mean that physical principles cannot be applied to a subset of the software development process. However, there are usually better ways to achieve ends in software if one is not constrained by paradigms adopted from the physical world. Even paradigms that are natives to the virtual world (like mathematics -> category theory, functional programming) have not gained the kind of widespread acceptance that one would think they ought to.
- ryanmarsh 9y agosoftware is a procedural epistemology that manipulates ideas that do not necessarily have to correspond to physical objects This is why I often argue software development is applied semiotics.
- QAPereo 9y ago"The map is not the territory." -Alfred Korzybski