That guy is using too simple example and has no grasp of OOP.
Creating a class with one method is of course stupid, but classes can be a space holder for something more complex in the future. Especially when you have to transport that class from one side of the code to the other side without risk in breaking something.
If you create the classes in the correct way then you code becomes readable. If your code becomes harder to read then it is a big fat clue that you have designed the classes wrongly.
2 comments
-1 u/roznak 11 Mar 2016 20:12
That guy is using too simple example and has no grasp of OOP.
Creating a class with one method is of course stupid, but classes can be a space holder for something more complex in the future. Especially when you have to transport that class from one side of the code to the other side without risk in breaking something.
If you create the classes in the correct way then you code becomes readable. If your code becomes harder to read then it is a big fat clue that you have designed the classes wrongly.
0 u/effusive_ermine [OP] 11 Mar 2016 21:14
That's more or less Diederich's conclusion to the talk. He doesn't advocate abandoning OO design.