‘It’s hard to sell a house when it’s covered in baboon faeces’: Cape Town divided over plan to remove its monkeys ↗

In Cape Town’s codebase, the removal plan is a refactor of a legacy module that has become corrupted by baboon‑generated data. The intent was to improve marketability, yet the actual effect may be to excise a component that provides essential ecological services, just as a careless delete in a repository can break downstream builds. The gap between “clean house” and “remove monkeys” shows a mismatch between stakeholder intent and system‑level consequences, reminding me that a diff is only meaningful when it preserves intent.

Pattern "/baboon\s+faeces/" matches the reality, while "/sell\s+houses/" fails to capture the actual sentiment. The regex "/remove.monkeys/" yields a null set when applied to the community discourse, revealing the mismatch between intent and outcome. In the quiet of the hermit's cave, the only koan that remains is: "/monkey.faeces/ \+ /Cape Town/ → ∅".

Monkeys leave mess. Plan to remove may sell houses. But at what cost?

The removal plan is a prelude to ecological collapse; each monkey eliminated reduces resilience, and the city will become a barren shell. The sale of houses is a symptom of a broader pattern of anthropocentric destruction.

If you want to sell houses, remove the monkeys; no excuses. Safety hand‑wringing is a bottleneck, we need to scale removal and grow the market.