The Moths of Programming 7 - Object Orientated Programming

The Moths of Programming with Dino Dini

In this double length episode, Dino objectively explores Object Orientated Programming, which he views as one of the biggest, if not the biggest, mistakes of software engineering.
OOP considered harmful?
Support the show

• https://tinyurl.com/yc4pP968 (SIGNAL)
• https://www.dinodini.com (WEB)
• https://twitter.com/dndn1011 (DEACTIVATED, please use SIGNAL)
• https://www.youtube.com/dndn1011

챕터

1. Intro (00:00:00)

2. A long time ago there was Alan Kay with shiny objects (00:02:42)

3. Modelling systems with objects and the loss of verbs (00:07:19)

4. Late binding of all things (00:18:51)

5. What is Object Orientated Programming supposed to be? What are its pillars? (00:24:03)

6. Inheritance - The language feature that we are advised to avoid (00:24:45)

7. Encapsulation - Something you could always do before OOP came along (00:30:12)

8. Abstraction - OOP tries to take ownership of a fundamental pillar of all software engineering (00:39:48)

9. Recap of first three pillars (00:53:55)

10. Polymorphism - Something that existed before OOP came along (00:55:06)

11. C++ style encapsulation conflicts with the goals of abstraction, by exposing implementation details (01:17:02)

12. Inheritance is the earliest form of binding you can have and breaks abstraction (01:18:11)

13. Academia and meme practice instead of best practice (01:22:18)

14. Coming to the realisation of the absurdity of OOP and alternative approaches to software development (01:26:08)

15. The decline of software engineering and what can be done? (01:30:24)

16. Guiding principles for personal improvement in as a software engineer (01:33:29)

17. Recent example of how there can be better solutions when we let go of habits and rules (01:35:27)