My Junior developer told me: OO Design patterns are too complicated and useless
<p>I learned a lot from our conversation.</p>
<h1>The conversation</h1>
<p>Weeks ago, lunchtime.</p>
<p>My junior told me: “I think OO programming does not make sense, It is always over complicated things.”</p>
<p>“Why do you think so?” I asked.</p>
<p>Dude: “You see it always needs to create a bunch of classes even for some straightforward task. I don’t like the idea of being forced to create some classes to finish things”. “for example you see our password validator logic, one function is enough, why even need a class?”</p>
<p>Me: “Agree. you don’t have to. but class hierarchies are just like abstraction tools. consider it as an abstraction of data + functions ‘package’. use them when needed, if not, just leave them. continue with the way which you think simple”.</p>
<p>Dude: “Yes, but I don’t understand why this class idea is even invented, and what are the OO design patterns for? so complicated, and also DI/IOC which seems not necessary”, “And, what is the MVC pattern? the web framework we are using?”, “I like the way how functional programming get things done, it is so simple and less side effect”.</p>
<p><a href="https://iorilan.medium.com/my-junior-developer-told-me-oo-design-patterns-are-too-complicated-and-useless-4dce902597f0">Click Here</a></p>