add public/keeper.jpg
Software design, explained by way of a beehive.
SOLID, the patterns, and the architecture arguments. Written for engineers who already ship and want the reasoning underneath.
Recently committed
Single Responsibility: One Bee, One Job
Why a class with two reasons to change has two reasons to break.
Open/Closed: Sweet as Honey but Closed for Modification
Extend the comb. Do not re-cut the cells you already filled.
The Observer Pattern: How the Hive Knows the Queen Moved
Broadcast without coupling: the dance, not the phone tree.
Don't Repeat Yourself (or the Hive Collapses)
Duplication is cheap today and structural debt by Thursday.
Who writes this
One engineer with too many opinions about coupling and a genuine interest in bees. Corrections welcome, pull requests better. Arguments about whether the Singleton counts as a pattern will be closed as wontfix.
MIT licensed. Reach the keeper at keeper@honeytrap.dev.
TERMINALPROBLEMSOUTPUT
Try:
honeytrap shell. Two commands are wired up: cd and cat.