Enforcing encapsulation with East-oriented Code
Preview text: Keep track of information flow and code maintenance will follow Hi! I'm Jim, the author of…
No image available for this email.
- Subject
- Enforcing encapsulation with East-oriented Code
- Preview text
- Keep track of information flow and code maintenance will follow Hi! I'm Jim, the author of…
- From
- jim@
saturnflyer.com - Brand
- Clean Ruby
- Sent
- Sat Jul 11, 2026, 12:36 AM ET
- Size
- 70 KB
- Images
- 2
- Links
- 8, 2 of them buttons
- Subject length
- 47 characters
Against Clean Ruby's usual
Sent in its busiest hour, 12 AM, which holds 97% of its emails. The subject is 47 characters; its average is 41.
Sent just before and after
| Aug 1, 2026 12:36 AM | Ruby Forwardable deep dive | |
| Jul 25, 2026 12:36 AM | Avoiding clever mistakes when displaying data with missing values | |
| Jul 18, 2026 12:36 AM | Get Clean Ruby | |
| Jul 11, 2026 12:36 AM | Enforcing encapsulation with East-oriented Code (this email) | |
| 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 |
More from Clean Ruby
All Clean Ruby emailsOct 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
Sep 13, 2026 12:52 AM







