Intentional complexity to slow down the incidental complexity curve is exactly what good frameworks are for. A solid framework introduces a lot of initial complexity, but provides you with well thought out and widely used (hence well debugged) solutions to problems you might encounter later as your project grows.
The distinction between incidental complexity and intentional complexity is a good point! Does anyone have a link to the talks of Gary Bernhardt that the speaker refers to....I may misspell the name but haven't been able to find anything!?
Intentional complexity to slow down the incidental complexity curve is exactly what good frameworks are for. A solid framework introduces a lot of initial complexity, but provides you with well thought out and widely used (hence well debugged) solutions to problems you might encounter later as your project grows.
The distinction between incidental complexity and intentional complexity is a good point! Does anyone have a link to the talks of Gary Bernhardt that the speaker refers to....I may misspell the name but haven't been able to find anything!?
Hey Timm,
Here is the link to Gary's talk: ruclips.net/video/yTkzNHF6rMs/видео.html
@@automaticpixel thanks☺
If anyone else is looking, search for "Gary Bernhardt Boundaries"
"Service objects: Stateless, and contain no data"
You mean, like functions? Why would you create a class which has no data and only one function?