132 likes
·
770 reads
22 comments
Helps me out. Thanks Priyanka
Thank you :)
I really enjoyed reading it! Loved your approach!
Thank you :)
Loved it. Especially the story part. 😄
Thank you Shad :)
This is a fantastic article. Thanks for sharing Priyanka Yadav.
Thanks you Edidiong Asikpo :)
Loved the way you approached!!
Thank you :)
Loved the concept of this article and well suits is love
Thank you :)
Priyanka Yadav, wow!! Loved the way you have explained things here.. So Cool!!
Thank you :) Glad you liked it
I love the way you explain both concepts as a story. Good read 👍
Thank you :)
Loved the story Priyanka Yadav. I have a question. What if the hierarchy of the company is fixed and we have only two types of associates and only their responsibilities can change, will OOP still be the better approach?
What if responsibilities change for the fixed hierarchy? The if-else comparisons would turn code messy.
Thanks for sharing! What an enjoyable read!
Thank you :)
relating it with suits, is surely something which i will try, other than that the article gives us a very narrow picture of oops v/s procedural programming, i am sure there is more to it :)
feel free to share your blog whenever you write, would love to study about the advanced concepts :)