|
|
|
|
|
by menotyou
965 days ago
|
|
I don't program myself, but I do manage developers for 20yrs+. I normally don't care about what paradigm programmers use, but what I do empirically observe is that time spend on (automated) testing, refactoring and bug fixing is much higher in an object oriented environment. It seems from outside that the ability of producing reasonably bug free code is much lower when using OOP, hence the need of faster deployment cycles. Other industries went the way of producing good quality products whereas IT seems to use the approach to test the quality into the products and to fix, quite often when product is already at customer. This normally turns out be more expensive and have less quality in the products at the same time. |
|
Hypothesis: software market has near zero barriers to entry, so while other industries are protected from would-be competitors by large up-front expenses, for most purely-software products anyone can rapidly build a half-assed clone of whatever you're doing and start eating into your customer base - making software companies obsess over velocity / feature delivery rate, and/or seeking all kinds of non-software barriers to entry (e.g. network effects, or content deals - like, it wouldn't be hard to make a better Spotify client, but good luck replicating the deals Spotify has with recording labels).