Quotes About Integration

The dance of Recovery is a process of learning to accept and integrate the Truth of Grace into our lives.

One of most important steps to empowerment is integrating Spiritual Truth into our experience of the process. In order to do that it is necessary to practice discernment in our relationship with the emotional and mental components of our being.

As a good housewife out of divers fleeces weaves one piece of cloth, a bee gathers wax and honey out of many flowers, and makes a new bundle of all... I have laboriously collected this Cento out of divers writers, and... I have wronged no authors, but given every man his own.... I can say of myself, Whom have I injured? The matter is theirs most part, and yet mine...

QA and Development should be working together to ensure the quality of the system. The

In fact, wrapping third-party APIs is a best practice. When you wrap a third-party API, you minimize your dependencies upon it:

In general, it is harmful to depend on modules that contain more than you need. This is obviously true for source code dependencies that can force unnecessary recompilation and redeployment—but it is also true at a much higher, architectural level.

This means that the UI and the database can be plugins to the business rules. It means that the source code of the business rules never mentions the UI or the database.

The architecture of a system is defined by a set of software components and the boundaries that separate them.

The team is working along at a certain productivity. Then new staff is added. Productivity plummets for a few weeks as the new people suck the life out of the old people. Then, hopefully, the new people start to get smart enough to actually contribute.

You should be able to run all the unit tests with just one command.

The tests fit the production code like an antibody fits an antigen.

Components are the units of deployment. They are the smallest entities that can be deployed as part of a system.

dynamically linked files, which can be plugged together at runtime, are the software components of our architectures.

Classes and modules that are grouped together into a component should be releasable together. The fact that they share the same version number and the same release tracking, and are included under the same release documentation, should make sense both to the author and to the users.

The source code of higher-level services must not contain any specific physical knowledge (e.g., a URI) of any lower-level service.

If component A should be protected from changes in component B, then component B should depend on component A.

One sure way to make a software component difficult to change, is to make lots of other software components depend on it.

Any comment that forces you to look in another module for the meaning of that comment has failed to communicate to you and is not worth the bits it consumes.

Notice how well those three align with the three big concerns of architecture: function, separation of components, and data management.

Building trust is no longer a matter of creating structures and practices within a single culture.

Everyone carries a shadow, and the less it is embodied in the individual's conscious life, the blacker and denser it is. —Carl Jung

Daily Law: Return to the harder or softer sides of your character that you have lost or repressed. The Laws of Human Nature, 12: Reconnect to the Masculine or Feminine within You—The Law of Gender Rigidity

Stop Being So Nice Everyone carries a shadow, and the less it is embodied in the individual's conscious life, the blacker and denser it is. —Carl Jung

Combine Your Fascinations