Timeline for Managing and organizing the massively increased number of classes after switching to SOLID?
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 11, 2019 at 19:49 | comment | added | Corrodias | Agreeing, I add this. To quote Wikipedia, "Martin defines a responsibility as a reason to change, and concludes that a class or module should have one, and only one, reason to be changed (i.e. rewritten)." and "he more recently stated "This principle is about people."" In fact, I believe this means that the "responsibility" in SRP refers to stakeholders, not functionality. A class should be responsible for changes required by only one stakeholder (person requiring that you change your program), so that you change as FEW things as possible in response to different stakeholders demanding change. | |
| S Jul 9, 2019 at 18:04 | history | suggested | Peter Mortensen | CC BY-SA 4.0 | Copy edited. |
| Jul 9, 2019 at 18:02 | review | Suggested edits | |||
| S Jul 9, 2019 at 18:04 | |||||
| Jul 9, 2019 at 14:23 | comment | added | John Bollinger | Again, @JDDavis, choosing multiple classes over a single one purely for testability purposes is putting the cart before the horse, and it goes directly against the SRP, which calls for grouping cohesive functionalities together. I can't advise you on particulars, but the problem that individual functional changes require modifying many files is an issue that you should be addressing (and attempting to avoid), not one that you should be trying to justify. | |
| Jul 9, 2019 at 14:14 | comment | added | JD Davis | I guess I'm just trying to figure out where the line is. In a recent task, I had to perform a fairly simple operation, but it was in a codebase without much existing scaffolding or functionality. As such, everything I needed to do was very simple, but all pretty unique and didn't seem to fit in shared classes. In my case, I needed to save a document to a network drive, and log it to two separate database tables. The rules surrounding each step were fairly particular. Even the filename generation (a simple guid) had a few classes to make testing more convenient. | |
| Jul 9, 2019 at 14:00 | history | answered | John Bollinger | CC BY-SA 4.0 |