I'm not sure if that choice would help you much. What drives code into being a mess really? I think it has more to do with wildly changing or unclear requirements, badly adopted scrum, having to deliver at any cost, forcing devs to so stuff they don't want to and so on. Using another programming approach wouldn't fix any of these.
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.
ttyyzz|2 years ago
porridgeraisin|2 years ago
menotyou|2 years ago
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.