---
title: "Comment by BridgeXAPI on \"How “Design Patterns Explained” Changed the Way I Design Software\" | Hashnode"
description: "\"What is stable, and what is likely to change?\" is probably one of the most useful architecture questions there is. We've been seeing something similar in BXRun"
url: "https://hashnode.com/posts/how-design-patterns-explained-changed-the-way-i-design-software/6a1f22bc545c8a206ce1f536/comment/6a1f30cd545c8a206ce8a23a"
---

[Discussion](https://hashnode.com/posts/how-design-patterns-explained-changed-the-way-i-design-software/6a1f22bc545c8a206ce1f536)

Comment [How “Design Patterns Explained” Changed the Way I Design Software](https://hashnode.com/posts/how-design-patterns-explained-changed-the-way-i-design-software/6a1f22bc545c8a206ce1f536)

[BridgeXAPI](https://hashnode.com/@bridgexapi)

[Jun 2](https://hashnode.com/posts/how-design-patterns-explained-changed-the-way-i-design-software/6a1f22bc545c8a206ce1f536/comment/6a1f30cd545c8a206ce8a23a)

"What is stable, and what is likely to change?" is probably one of the most useful architecture questions there is. We've been seeing something similar in BXRuntime recently. Several systems evolved independently, but once we started isolating what changes over time, a very different architecture emerged than the one we originally planned.

Great read.