Timeline for Are there flavours of OOP where some or all of the SOLID principles are antithetical to clean code?
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 7, 2016 at 6:31 | comment | added | sara | @Andy not necessarily. at my current job, a lot of the worst parts of the code is messy because it's just thrown together by "doing something simple, just hack it together and get it working so it doesn't get so complex". As a result, many parts of the system are 100 % rigid. You can't modify them at all without rewriting large parts of them. It's really hard to maintain. Maintainability comes from high cohesion and low coupling, not from how flexible the system is. | |
| Apr 6, 2014 at 23:51 | comment | added | Andy | +1 By definition almost, a highly flexible system must be less maintainable than one which is less flexible. Flexibility comes at a cost due to the added complexity it brings. | |
| Apr 4, 2014 at 21:09 | history | answered | henginy | CC BY-SA 3.0 |