Medium - Object-Oriented Programming — The Trillion Dollar Disaster - 3
in Trend
Trend 파악을 Medium 기고문 요약 포스팅 - OOP, 막대한 금전적 재앙 3
Unit Testing
Photo by Ani Kolleshi on Unsplash
Boilerplate code
Testing private methods
Refactoring
The Band-aids
Image source: Photo by Pixabay from Pexels
Design patterns
The problem factory
Image source: https://www.reddit.com/r/ProgrammerHumor/comments/418x95/theory_vs_reality/
The Fall of the Four OOP Pillars
Inheritance
I think the lack of reusability comes in object-oriented languages, not in functional languages. Because the problem with object-oriented languages is they’ve got all this implicit environment that they carry around with them. You wanted a banana but what you got was a gorilla holding the banana and the entire jungle. \— Joe Armstrong, creator of Erlang
OOP polymorphism
Encapsulation
Abstraction
Why Does OOP Dominate the Industry?
Photo by Gaetano Cessati on Unsplash
Java was Simple
Then C# came along
Functional languages
Time to Move On?
We now know that OOP is an experiment that failed. It is time to move on. It is time that we, as a community, admit that this idea has failed us, and we must give up on it. - Lawrence Krubner
Photo by SpaceX on Unsplash
What Are the Alternatives?
Photo by Harley-Davidson on Unsplash
The Defenders of OOP
Photo by Ott Maidre from Pexels
