Quotes About Application

I had applied to become French - or, rather, Franco-American, as I'm now a dual citizen - partly because I could: I'd lived and paid taxes here for long enough.

I just think it would be interesting. I already applied to be a substitute teacher.

I don't like to be negative about math because it really teaches you a lot of great things. You kind of use math every day.

Knowledge without application eventually becomes boring and unfulfilling

The Bible] has to be interpreted. And if it isn't interpreted, then it can't be put into action. So if we are serious about following God, then we have to interpret the Bible. It is not possible to simply do what the Bible says. We must first make decisions about what it means at this time, in this place, for these people.

Event sourcing is a strategy wherein we store the transactions, but not the state. When state is required, we simply apply all the transactions from the beginning of time.

The promise to try is an admission that you've been holding back, that you have a reservoir of extra effort that you can apply.

In fact, component dependency diagrams have very little do to with describing the function of the application. Instead, they are a map to the buildability and maintainability of the application.

Jacobson makes the point that software architectures are structures that support the use cases of the system. Just as the plans for a house or a library scream about the use cases of those buildings, so should the architecture of a software application scream about the use cases of the application.

The web is a delivery mechanism—an IO device—and your application architecture should treat it as such. The fact that your application is delivered over the web is a detail and should not dominate your system structure. Indeed, the decision that your application will be delivered over the web is one that you should defer. Your system architecture should be as ignorant as possible about how it will be delivered.

A shopping cart application with a good architecture will look like a shopping cart application. The use cases of that system will be plainly visible within the structure of that system. Developers will not have to hunt for behaviors, because those behaviors will be first-class elements visible at the top level of the system.

So what does the architecture of your application scream? When you look at the top-level directory structure, and the source files in the highest-level package, do they scream "Health Care System," or "Accounting System," or "Inventory Management System"? Or do they scream "Rails," or "Spring/Hibernate," or "ASP"?

You must understand that when you marry a framework to your application, you will be stuck with that framework for the rest of the life cycle of that application. For better or for worse, in sickness and in health, for richer, for poorer, forsaking all others, you will be using that framework. This is not a commitment to be entered into lightly.

Theoretically, the procedure might be more stable if it was applied to a human fetus in vivo. An unborn child in the womb.

Reading and thinking about [new ideas] won't work. You must put them into effect.

Understanding, like a muscle, increases with use. The more you use it the more you have. That is why problems are interesting. They help you to apply your knowledge and to prove the Law. If it were not for your problems, you would vegetate. You would have no way of using or applying the Truth.

Many people want these government loans, but very few people qualify for them

Most teachers lack real-world experience—they have not done what they teach. They haven't actually experienced what they teach, made mistakes, learned from those mistakes, and applied what they've learned as they continue to practice and get better and better. Schools teach us to read and memorize. I believe that 'studying' is the key to applying what we learn. Kim and I meet with our Advisors several times a year and we choose books to read and study together.

THE CONE OF LEARNING Edgar Dale gets credit for helping us to understand that we learn best through action—doing the real thing or a simulation. Sometimes it's called experiential learning. Dale and his Cone of Learning tell us that reading and lecture are the least effective ways to learn. And yet we all know how most schools teach: reading and lecture.

Science and everyday life cannot and should not be separated.

Science does not have a moral dimension. It is like a knife. If you give it to a surgeon or a murderer, each will use it differently.

All models are wrong, but some are useful.

To the engineer falls the job of clothing the bare bones of science with life, comfort, and hope.

Engineering is the art or science of making practical.