Yes, however there’s circumstances for when it’s most effective. For example: Large systems benefit from clear architectural patterns, whereas small systems se

Yes, however there’s circumstances for when it’s most effective. For example: Large systems benefit from clear architectural patterns, whereas small systems see little benefit Performant code is often obscure and messy, it shouldn’t be forced into a “clean pattern” for the sake of it Clean architecture greatly affects how changes are made in the system. If 20 places need to be updated to add a feature, and that’s something that needs to be done often, then maybe refactoring it would improve this workflow. At the end of the day it’s a tradeoff that programmers need to make “will cleaning this up make it better or worse for us”