yogsototh/deft
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

notes/2021-03-14--13-00-04Z--the_service_pattern.org

Browse source
This commit is contained in:
Yann Esposito (Yogsototh) 2021-10-31 16:14:23 +01:00
parent ebb5c799f3
commit 59ad4d4dc1
Signed by untrusted user who does not match committer: yogsototh
GPG key ID: 7B19A4C650D59646
1 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
notes/2021-03-14--13-00-04Z--the_service_pattern.org
View file

@ -25,8 +25,8 @@ language.
Before explaining the pattern I would like to take the time to provide a
few distinctions between different programming language patterns.
Quite often, one fundamental question very important when choosing a
pattern for your code is about find the correct level of the pattern.
Quite often, one fundamental question when choosing a pattern for your code
is about finding the correct level of the pattern.
There are a tower of patterns and meta-patterns.
For example in imperative programming not using =goto= statement was
@ -34,7 +34,7 @@ considered as a programming pattern.
Once that idea was accepted there were work done on /Object Oriented
Programming/.
And OOP was considered as a programming language pattern.
But OOP while already providing quite a constraint on your code
OOP while already providing quite a constraint on your code
architecture was enough not sufficient.
OOP alone leave a lot of room in the design space.
Thus we've seen numerous "OOP Design Pattern".
@ -45,7 +45,7 @@ Even with all those Design Pattern it was up to the programmer to decide
which one applies or not.
Quite often there is not a single path easy to detect correct design
pattern.
Mainly the very hard part in programming is choosing the right abstraction.
Mainly the hard part in programming is choosing the right abstraction.
There are other code structures to choose from.
In functional programming there are FRP.