I want a movie on this.

If anything I would evidence the sentence after that.

@Pickman People who are lazy to learn patterns and use them correctly will also use that next sentence as a reason to not use them at all.

Designe patterns are bandaids, so something must be bleeding. Eighter the programming language, OOP or all programmers. Pick your personal bias: https://youtu.be/QM1iUe6IofM https://youtu.be/V6VP-2aIcSc https://youtu.be/IRTfhkiAqPw

@netikras which is still better than applying patterns lazily.

@Pickman I'd argue with that. Writing a 20k loc application in a single file vs. writing a 20k loc application applying a poorly chosen pattern. I'd definitely go with the latter

@netikras I think it depends on two things.
1. How bad a fit the pattern is (it could lead to code that just misses the necessary requirements).
2. How badly implemented the design pattern is. I've seen people who decided to use a design pattern and then implemented them so lazily that the final result was not that design pattern at all. In fact most implementations I've seen have this problem.
P.s. design patterns have nothing to do with files. No, they simply do not.

@Pickman sorry, I'm speaking from java point of view, so patterns do very closely relate to files :)

@netikras well, not necessarily but it probably should be good practice.