Re: Convincing management for OO

OO scripts can be copied and modified as easy as procedural ones. What you should introduce is modularity. They are different concepts. They work hand in hand and favour each other, but they are different concepts.

choroba's advice about proof of concept is good in any case. Show your managers (and/or your Senior colleagues) how building a library of modular, reusable routines can help. If you then still want to further OO, you can build upon how it supports modularity.

Comment on Re: Convincing management for OO

Replies are listed 'Best First'.
Re^2: Convincing management for OO by Anonymous Monk on Mar 03, 2017 at 03:06 UTC
yes, you are right. OO is just one way of achieving modularity. Reading data, processing, outputting/formatting are in a single script...for all existing scripts. :(	[reply]
Re^3: Convincing management for OO by soonix (Chancellor) on Mar 03, 2017 at 08:09 UTC
That's your starting Point: compare the variants of those functions that you want to centralize by your module to find out how you should parametrize them. Then, instead of copying and modifying, set a good example by copying and creating a module (and, of course, eventually using that). This will take more time, so you might have to do it alongside, but once it is usable, you can use it to convince your colleagues (I don't think your management mandates copy-paste-programming) to take this road. Of course, further adaptations/modifications of the new "central" module can break those scripts that already rely on it, so it's important to include at least rudimentary tests, lest it will be turned into an argument against modularization…	[reply]