Believe me, I do think in terms of business domain problems first. One of my customers' primary concerns is ensuring that their data is consistent. Always. They

Believe me, I do think in terms of business domain problems first. One of my customers' primary concerns is ensuring that their data is consistent. Always. They make very expensive decisions based on the consistency of that data. If they have to shut down a plant because a value was off they lose millions of dollars. I see our customers' data as our core and any code we write as a liability. We're constantly looking for ways to reduce our liability and ensure our customers' data will always be consistent. We push all of our business logic down to the database layer where the RDBMS server is responsible for ensuring its consistency and integrity. While we're not perfect we do have some business logic in our web processes. However for the most part the job of that component is to parse HTTP queries into queries on our public schema. If we wrote business rules into our software it would be very difficult to verify them, search for them, and keep track of how they've changed over time. It's also too easy for a programmer to make an error which could cause our customers' data to enter into an inconsistent state or worse. We avoid that as much as possible.