Thank you! You are really highlighting what the principle is about - scenarios and consequences. And I totally agree on the factors making you violate the principle (which of course is a guideline - a good one if to maintain software)
@teamtosoz892 I am not sure what exactly u r referring to - in this video i didn't talked about controllers and use cases. Could u pls explain in a bit more detail?
I often prefer to improve design as the project grows and comes to actually need the design improvements. I've found over-designing early on tends to backfire, as that over-design ends up having to be re-done to actually meet my changing needs. Note: not uni educated, been developing foss php for years, but all on my own. No big corp or team experience. And most my past opinions on design have changed ... so this opinion may too lol.
I agree, creating a big design up front often results in over-complicated designs. The challenge is to find the "right point in time" when to improve the design as the project grows - and here i prefer to choose an earlier point in time over a later one.
