4 ms·
> But collecting the models, the different representations of systems conceptually that can be expressed as software, sometimes called paradigms: this is very i
by criddell 9y ago
> But collecting the models, the different representations of systems conceptually that can be expressed as software, sometimes called paradigms: this is very interesting.
Isn't this another way of saying design patterns? I know the answer has to be "no", but I don't see why.
- aryehof 9y agoUnfortunately "design patterns" for most, means technical programming language patterns, rather than the patterns found in "problem domains" outside of computing that can be repeatedly and predictably modeled into code. They do exist, but are very rarely known. Take object-orientation. Typically the primary pattern known is just object, class and inheritance. However, there are patterns that build on those to model the things, people, places, events and concepts, and the roles they interact in, and the constraints that limit them, in every "business" or real-world domain. Why aren't they better known? I think it is because object modeling has entirely lost the battle today to data modeling, where data entities are acted on by external code organized using functional decomposition. It doesn't seem to bother most that for 45 years we have been struggling with the problem that doing so increasingly results in a "big ball of mud" as project size and complexity increases.
- cocoablazing 9y agoWe maintain a lightweight platform alongside a legacy platform that is an untestable ball of mud. This resulted from rapid implementation of business demands over the years, along with a practice of addressing numerous data quality problem through hacks in components, rather than cleaning the data or using a sanitization layer to access it. Lack of dependency inversion in systems like this is truly the road to ruin, as the system complexity grows so quickly in time, due to interactions, that eventually nobody really understands what it does or why it does it. I suppose this is tolerable for some applications, but if you need to numerically validate it, it's a nightmare.
- mpweiher 9y agoNot really, no. Paradigms are quite a bit broader. One definition/explanation: https://www.info.ucl.ac.be/~pvr/VanRoyChapter.pdf https://www.info.ucl.ac.be/~pvr/VanRoyChapter.pdf They also have a nice book: https://www.info.ucl.ac.be/~pvr/book.html https://www.info.ucl.ac.be/~pvr/book.html I personally think the notion of architectural style is more useful.
- bitwize 9y agoModels are the substrate on which design patterns are built. Most of the design patterns you know are based on an object-oriented model. Functional programming presents a different model, with its own set of patterns (of which, for example, "monad" is one).
- nextos 9y agoNo. Aside from the excellent link to Peter Van Roy's work someone else posted in this tree, take a look at http://wiki.c2.com/?ThereAreExactlyThreeParadigms http://wiki.c2.com/?ThereAreExactlyThreeParadigms.
- PuercoPop 9y agoI'd say no, design patterns are about mechanism, 'I want to do X, this pattern is how I do it'. In that way they are similar to monads. Pardigms are about a perspective, a vantage point from which you structue your application. Say dataflow programming, for which Norvig's sentence generator in PAIP is an excellent introduction, one can use a switch/case or an object with functions as values. Both accomplish the same, but in the latter I change the flow of my program by changing a value in a map.
- emmelaich 9y agoSame thought occurred to me but upon reflection perhaps they're different levels of the same thing. tricks->idioms->techniques->patterns->paradigms->...?