Is it worth applying the OOP paradigm in each task assigned by the customer?

Question

OOP

Question for professional software developers or developers with experience. I can not understand why it is reasonable to use OOP in every task. Is it possible to use OOP only when you understand that the task is difficult (or something in the middle)? Does it depend on the programming language? Well, for example, C# is already an oops language .. I think it was difficult to explain, I will be glad if you answer.

Answer 1

No, it's not worth it.
OOP is needed to simplify complex tasks, to simplify long-term support.
If you have a simple one-time task, then no one forces you (unless it is specified when setting the task).
Just say this to the customer: let me start code for you here quickly, or pay extra for OOP + 50% !!!!

Answer 2

It is worth applying the OOP paradigm in each task

definitely not

It is worth using the OOP paradigm

KISS, those if not using the approach complicates the code
The complexity of the task is a subjective measure
To evaluate the application of a particular paradigm, you need to evaluate the complexity of the implementation
The paradigm should reduce the complexity of the implementation and, as a result, make it easier to understand, read the code and write code

Answer 3

In my purely personal opinion: Rather worth it than not.
Although the comrades above expressed themselves differently, I will explain why.
1. Yes, it all depends on the language. The same sharp is already crazy, and Java too.
If we are talking about languages ​​that support both procedural and OOP programming, then, of course, everything depends on the task, and when it takes two lines of code, then it makes no sense to fence classes, interfaces, etc., but here it comes into force point 2
2. As sim3x rightly said , the complexity of the task is a subjective question, personally, if I understand that there will be at least 100 lines of code, I already organize the normal architecture of the project. even if it is a one-time craft and you don’t have to maintain it. So personally, it's more pleasant for me to work.
Well, you need to remember that you need to resort to automating anything only if the time to implement this very automation does not exceed the time spent on completing the task without writing code. So is the approach to organizing the project: if it takes half a day to form the structure and prepare the base, and the business logic itself takes 15 minutes, then the question of expediency arises. It's just that in practice I personally have not yet come across such small tasks.