Link Details

This is true and should also be extended to the situations were patterns are overused in order to achieve clean code to the detriment of performance, readability etc. The database loop example the guy gives is something that happends so often, it makes you wanna cry. I've had 7-8 yeard old experienced developers lecturing me about "clean and structured code, not one line not belonging to this or that pattern" and then getting their code that used like visitors and coarse grained/fine grained DTOs (aspect managed none the less), to load a list of entities with ALL their properties and associations for display in a list, and then reloading each one when it was clicked inside that list to have all the previously loaded properties and associations displayed. And when (ofcourse) the performance issue hit, they added even more pattern based code and other crap to make some kind of in memory cache for those objects that were retrieved 5 times over and over each. And no, it was not the fault of the ORM "hiding the complexities and forcing wide eyed innocent developers inadvertently write bad code" because there was no ORM or database to speak of, it was a plain old Alfresco repo that just returned tuples for all your values.