Timeline for Documenting my abstract class/interface - what is important?
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 21, 2022 at 12:28 | comment | added | Brian Karabinchak |
1) Thank you for the tip about __resetResults - having a convention like that would help know which is to be overwritten and what is not to be. 2) I never heard of the Template Method Pattern - I'm glad what I am doing is an established pattern and not an established anti-pattern lol. However, this does give me a a new rabbit hole to go down so I greatly appreciate it!
|
|
| Jun 20, 2022 at 16:50 | comment | added | gnasher729 | Interfaces have no code, therefore they cannot have self-documenting code. And the code would self- describe what it does, which isn't helpful because you need to know what other code following the same interface does. | |
| Jun 20, 2022 at 16:18 | history | edited | Cwt | CC BY-SA 4.0 |
Improve readability with formatting
|
| S Jun 19, 2022 at 16:03 | review | First answers | |||
| Jul 3, 2022 at 16:03 | |||||
| S Jun 19, 2022 at 16:03 | history | answered | Cwt | CC BY-SA 4.0 |