T3’s modular approach to applications allows you to focus on building small pieces of functionality.
T3 components can be developed and tested independently, making it perfect for large, distributed teams.
One of T3’s core goals is to prevent mistakes before they happen, by making it difficult for developers to do the wrong thing.
T3's design enforces best practices such as loose coupling by limiting how certain components can communicate with each other. Modules cannot interact directly with other modules but may communicate with them through an event bus. Modules may use services directly, but may only reference behaviors in a declarative way. These restrictions ensure that the various pieces remain loosely-coupled to make dependency management easy and maintenance self-contained.
The loosely-coupled nature of T3 components means that creating tests is easy. Dependencies are injected into each component, making it trivial to substitute a mock object in place of real ones.