Nice descriptions! And putting OO last is correct. A good language can do all four paradigms, but I find OO is easiest to work with as it avoids the "Hell's Half Acre" style of programming where everything related to solving a particular problem is scattered across the entire code base. Naming conventions help, but objects concentrate thing in specific places so you can understand all the logic together.
Most people fail in OO development because they never understand IS A and HAS A relationships and tend to do huge inheritance trees when trying to solve a HAS A issue. Inheritance should not be widely used in OO development. If you can solve it with HAS A, you should.
This is a very nice article. The way you explain your points makes them really understandable. Nice post.
This is a wonderful article, thank you for explaining most programming paradigms, I think I am now beginning to understand that programming is not about language or code, it's about understanding things like this and how you use them at scale, its also what makes you a senior developer
matt wilkie
a hewer of maps
There seems to be something missing at "For example: That code there is terrible,..." What code?