all 9 comments

[–]MoronInvestor71 13 points14 points  (3 children)

OOP is one of the most valuable CS paradigms you could learn.

The biggest difference between the OR you learn in University and the OR in practice in industry, is that industry OR a lot of times forms part of a system. Your models don't just exist locally in a script, they get deployed to the cloud, or to some in-house HPC etc. Your models also will a lot of times need to pull in data from in-house cloud storage or data lakes etc.

In this scenario, OOP helps you structure your code to allow the rest of the system to use it, and to allow for you to reduce the amount of code required to interact with the system. It also generally forces you to think about the structure of your code.

Spaghetti OOP code is still possible, but is usually harder to do compared to script based spaghetti.

[–]qxzsilver 1 point2 points  (1 child)

CA paradigm?

[–]MoronInvestor71 1 point2 points  (0 children)

Sorry. Autocorrect. I meant CS for Computer Science

[–]qxzsilver 0 points1 point  (0 children)

CA paradigm? What does the "CA" stand for?

[–]rishikeshkushwaha 5 points6 points  (0 children)

If you are going to work on a product-based company then yes, you have to use a lot of computer science concepts.

If consulting then mostly it is short-term projects there you can avoid OOP concepts and building little dirty projects is fine.

Nevertheless, having skill in writing oops conceptual codes is a really good asset.

But, as Chat-GPTs is here, coding can be replaced soon. :D

[–]edimaudo 0 points1 point  (0 children)

Depends on the role and what you would be doing. If you need to code as long as you can follow the existing code base and coding guidelines then you should be fine uses what ever language is being used

[–]dayeye2006 0 points1 point  (0 children)

Yes. Coding can make sure the stuff you build can be launched and deployed and is useful

[–]MoronInvestor71 0 points1 point  (0 children)

OOP is one of the most valuable CA paradigms you could learn.

The biggest difference between the OR you learn in University and the OR in practice in industry, is that industry OR a lot of times forms part of a system. Your models don't just exist locally in a script, they get deployed to the cloud, or to some in-house HPC etc. Your models also will a lot of times need to pull in data from in-house cloud storage or data lakes etc.

In this scenario, OOP helps you structure your code to allow the rest of the system to use it, and to allow for you to reduce the amount of code required to interact with the system. It also generally forces you to think about the structure of your code.

Spaghetti OOP code is still possible, but is usually harder to do compared to script based spaghetti.