[br3w5]

Avoiding all that "fancy unicorn stuff" might not slow you down but it will slow down the next person who picks up your code but who cares that's their problem.

You must come from the same school as "who needs tests they're a waste of time".

[MrLeftHand]

By calling it "fancy unicorn stuff" I mean, it is really hard to come by in real life. Because generally people avoid it and when they don't, they usually use it in a completely wrong way. I saw a Singleton pattern which made me carve my eyes out. And that came from a guy, who was a Senior Developer. And most of the times being a developer is about working with legacy code and trying to fix loads of problems, which wont be fixed in the end because there is not enough time, money and energy and so on and so on and... This makes loads of experienced people move in to management, or creating their own business, because they had enough of the trench work. That's why you won't see talented people on the market. Because they know...

Oh and no, I'm not from that school. But having tests doesn't mean the tests are any good. You can have loads of methodologies, patterns, principles. If you can't tell when to use a Factory Pattern, or how to implement SOLID, then it doesn't matter how much you like, or want them.

[br3w5]

Ok I retract my tests comment!

Design patterns can definitely be abused and pragmatism is important when deciding whether or not to use them. I would say though that implementing SOLID is certainly achievable if writing from scratch but harder when refactoring code that breaks those principles (usually badly with no tests or poor tests).