Timeline for What's the name of the principle that a method should EITHER orchestrate OR do?
Current License: CC BY-SA 4.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 2, 2021 at 15:12 | comment | added | bdsl |
@BernhardBarker Yes. Even if that library is <stdio.h>.
|
|
| Mar 2, 2021 at 14:56 | comment | added | Bernhard Barker |
I would call that a general guideline and one possible way to split up methods more so than a rule to be strictly followed (which applies to most of programming anyway). If, for example, checkDispensing just consists of a single line of code that isn't used anywhere else, then having a separate method for that probably just makes the code harder to understand and maintain. What is and isn't "perform tasks" probably also isn't that clear. You'll almost always use some library to access a DB or files or whatever, in which case the library's methods are arguably performing the tasks.
|
|
| Mar 2, 2021 at 11:48 | history | answered | Thom | CC BY-SA 4.0 |