Forwarding messages with Tell, Don't Ask
Preview text: Get prepared for requirements changes by using commands Hi! I'm Jim, the author of Clean…
No image available for this email.
- Subject
- Forwarding messages with Tell, Don't Ask
- Preview text
- Get prepared for requirements changes by using commands Hi! I'm Jim, the author of Clean…
- From
- jim@
saturnflyer.com - Brand
- Clean Ruby
- Sent
- Sat Jun 20, 2026, 12:37 AM ET
- Size
- 97 KB
- Images
- 2
- Links
- 8, 2 of them buttons
- Subject length
- 40 characters
Against Clean Ruby's usual
Sent in its busiest hour, 12 AM, which holds 97% of its emails. The subject is 40 characters; its average is 41.
Sent just before and after
| Jul 11, 2026 12:36 AM | Enforcing encapsulation with East-oriented Code | |
| Jul 4, 2026 12:36 AM | Preferring value objects or setters and arguments | |
| Jun 27, 2026 12:37 AM | Managing change using a common interface | |
| Jun 20, 2026 12:37 AM | Forwarding messages with Tell, Don't Ask (this email) | |
| Jun 13, 2026 12:37 AM | Avoiding errors when forwarding to missing objects | |
| Jun 6, 2026 12:37 AM | Shorter, simpler code with Forwardable | |
| May 30, 2026 12:35 AM | The tools that are right under your nose |
More from Clean Ruby
All Clean Ruby emailsThe easiest way to handle displaying bad data
Nov 2, 2026 12:05 AM
Oct 26, 2026 12:05 AM
OOP, DCI, and Ruby - what your system is vs. what your system does
Oct 19, 2026 12:04 AM
4 Simple Steps - Extending Ruby Objects - The Tip of the Iceberg with DCI
Oct 12, 2026 12:04 AM
Oct 10, 2026 7:07 AM
What if we organized code by features?
Sep 28, 2026 12:51 AM
Get a Clean Ruby discount before it's gone
Sep 21, 2026 12:51 AM
Cohesive behaviors with data clumps
Sep 20, 2026 12:51 AM







