Composition over inheritance (it's a really simple idea that some people might use naturally without realizing) Is dependency injection a design pattern? I've used the builder pattern and singleton (cue debate) in my previous Java life
None
Common sense design pattern
I make sure to utilize as many interfaces, facades, adapters and just design patterns in general as possible. All code should be obfuscated behind as many java classes as possible. This is what it means to code well
Don’t you think that creates unnecessary complexity. I see many times people make interfaces with just one impl. That never makes sense to me.
Umm... I think you missed Amazon's implicit /s tag
I’ve used pretty much all patterns out there. Whatever fits the need of what I’m building. However patterns are something that appear after really studying a problem. Often times people make noob mistakes by forcing their code into a design pattern for the sake of a pattern when the KISS/POLA principle would lead to something far simpler.
Strategy is most common because most of the time people don’t know what they are doing or we have a hack it now fix it later mentality. Composition over inheritance, when it makes sense like it has a vs is a relationship. Interfaces through delegation. Any other patterns are largely used for library development
SOLID