You can use all the classes, patterns, functions, methods you want but if it's not readable it's garbage.
but if it’s not readable it’s garbage.
Readability is often in the eye of the beholder, but knowing that a component implements a design pattern is all you need to know how it's used without even having to peek at the code.
I think the most vocal critics of design patterns are those who are clueless about design patterns, and they are criticising their use just because they are scared of stuff they don't know.
I like all of the concepts I listed btw. They can all make readability better of course.
You can use all the classes, patterns, functions, methods you want but if it's not readable it's garbage.
Readability is often in the eye of the beholder, but knowing that a component implements a design pattern is all you need to know how it's used without even having to peek at the code.
I think the most vocal critics of design patterns are those who are clueless about design patterns, and they are criticising their use just because they are scared of stuff they don't know.
I like all of the concepts I listed btw. They can all make readability better of course.