---
title: "Comment by Adam Lewis on \"CUPID Beyond SOLID: Five Properties for More Habitable Code\" | Hashnode"
description: "Domain-based is the property I've found hardest to retrofit. Names inside a file can be fixed a function at a time. A repository organised into controllers, ser"
url: "https://hashnode.com/posts/cupid-beyond-solid-five-properties-for-more-habitable-code/6a8f432846de88421a9d7742/comment/6a97f21e9b38ae5fff6598a1"
---

[Discussion](https://hashnode.com/posts/cupid-beyond-solid-five-properties-for-more-habitable-code/6a8f432846de88421a9d7742)

Comment [CUPID Beyond SOLID: Five Properties for More Habitable Code](https://hashnode.com/posts/cupid-beyond-solid-five-properties-for-more-habitable-code/6a8f432846de88421a9d7742)

[Adam Lewis](https://hashnode.com/@nark3d)

[Sep 2](https://hashnode.com/posts/cupid-beyond-solid-five-properties-for-more-habitable-code/6a8f432846de88421a9d7742/comment/6a97f21e9b38ae5fff6598a1)

Domain-based is the property I've found hardest to retrofit. Names inside a file can be fixed a function at a time. A repository organised into controllers, services and repositories has to be moved wholesale before a single business change stops being scattered across it, and that is work nobody budgets for.

It matters more now that an agent reads the tree before it reads anything else. A top-level checkout directory tells it where a change belongs.

The comparison table is a good addition, particularly the row on how each set fails once it turns dogmatic.

[prickles.org/tenet/screaming-architecture/A1](https://prickles.org/tenet/screaming-architecture/A1)
