Quotes About Implementation

The goal of the architect is to create a shape for the system that recognizes policy as the most essential element of the system while making the details irrelevant to that policy. This allows decisions about those details to be delayed and deferred.

Frameworks are tools to be used, not architectures to be conformed to. If your architecture is based on frameworks, then it cannot be based on your use cases.

Databases should usually not be considered as a major factor of the design and implementation.

During this design process, we rarely considered whether we were performing analysis, design, or implementation

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

But reflection without action is ultimately as unproductive as action without reflection.

The challenge is to maintain a high-level, broad perspective, understand enough details to make sensible and executable decisions, and then delegate responsibility for implementation. "Microknowledge" must not become micromanagement, but it sure helps keep people on their toes when they know that the secretary knows what the hell he's talking about. If the secretary of defense doesn't

The more frequently you intrude, implicitly reminding them it is your change, the less they will believe it is theirs. Successful implementation, in short, depends upon them. The leader cannot hold individuals accountable for driving change if he refuses to let go of the steering wheel. He must trust his subordinates, replace them if necessary. But he mustn't micromanage them.

A final, and critical, technique for implementing change is ensuring follow-through.

To be successful agents of change—of reform—leaders not only must be able to envision a new way forward but also must be practical, with the skill to build broad support for and implement their vision.

The next trick was to have the discipline to actually put into action what I had learned.

I think one's feelings waste themselves in words; they ought all to be distilled into actions which bring results.

For one person who is blessed with the power of invention, many will always be found who have the capacity of applying principles.

Anyone can write a specification, but if nobody implements it, what is it but a particularly dry form of science fiction.

every successful hardware has a software behind

These days, the problem isn't how to innovate; it's how to get society to adopt the good ideas that already exist.

It is one thing to conceive a good plan, and another to execute it

Learning has to come from doing, not intellectualizing.

So many decisions are destroyed by people's discussion on problems about the implementation. He worked always on the basis of let's get the principle agreed first and then farm out the implementation to somebody else.

I prefer trying over talking.

The government should set a goal for a clean environment but not mandate how that goal should be implemented.

However, the major issue is not how many of these books are purchased but how many get used. Our Debased Head Honcho would prefer that many of them be acquired then set on a shelf to gather dust. That's better than having only a few purchased but each of them carefully studied and the implemented.

However, the major issue is not how many of these books are purchased but how many get used. Our Debased Head Honcho would prefer that many of them be acquired then set on a shelf to gather dust. That's better than having only a few purchased but each of them carefully studied and then implemented.

a whole lot of ideas isn't a plan. A plan is a bunch of details that mesh with one another, so you go from this step to this step like crossing a stream on a lot of little boulders sticking out, and never fall in. Ideas without a plan is usually just enough boulders to get you into the deep part of the stream, and no way to get back.