Timeline for Are "need to call objects in parent object" and "avoid circular dependency" reasons to avoid "Tell, don't ask"?
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 28, 2023 at 16:58 | history | protected | gnat | ||
| Sep 28, 2023 at 16:33 | answer | added | user435221 | timeline score: 0 | |
| Sep 27, 2023 at 19:34 | answer | added | candied_orange | timeline score: 4 | |
| Sep 27, 2023 at 17:21 | answer | added | Mooing Duck | timeline score: 9 | |
| Sep 27, 2023 at 14:13 | history | became hot network question | |||
| Sep 27, 2023 at 10:22 | answer | added | Simon B | timeline score: 28 | |
| Sep 27, 2023 at 8:35 | comment | added | Rik D | Alternatively, you could consider a more loosely coupled pub/sub design, where Led, Speaker and Screen subscribe to some TemperatureLimitExceededEvent | |
| Sep 27, 2023 at 8:24 | comment | added | Rik D | Just as in real life, managers are often redundant ;-) Why don't you move Led, Speaker and Screen into SystemMonitor? | |
| Sep 27, 2023 at 6:06 | history | asked | wcminipgasker2023 | CC BY-SA 4.0 |