Quotes About Flexibility

It is better to manage changes skillfully than to just let life happen to you.

Life is like sailing. You can use any wind to go in any direction.

As a job seeker, remember this: You only lack experience if they want it done the same old way.

Optimist: someone who figures that taking a step backward after taking a step forward is not a disaster, it's a cha-cha.

Do what you must, And your friends will adjust.

A rule that cannot be bent will certainly be broken.

In a houseful of toddlers and pets, you can start out having a bad day, but you keep getting detoured.

You live long enough in a world spinning on its axis, you learn to spin in the same direction.

Model. Two mobile eyes in a mobile head, itself on a mobile body.

The best laid schemes o' mice and menGang aft a-gley.

The best-laid schemes o' mice an 'menGang aft agley.

The best laid schemes o' mice an' men/Gang aft agley" (En iyi planlar? farelerin ve insanlar?n/S?kça ters gider)

They have cheveril consciences that will stretch.

Make a virtue of necessity.

The true professional knows that delivering function at the expense of structure is a fool's errand. It is the structure of your code that allows it to be flexible. If you compromise the structure, you compromise the future.

Change is inevitable — except from a vending machine.

Change is inevitable--except from a vending machine.

If a change to the requirements breaks your architecture, then your architecture sucks.

What if your company has made a commitment to a certain database, or a certain web server, or a certain framework? A good architect pretends that the decision has not been made, and shapes the system such that those decisions can still be deferred or changed for as long as possible. A good architect maximizes the number of decisions not made.

The fundamental assumption underlying all software projects is that software is easy to change. If you violate this assumption by creating inflexible structures, then you undercut the economic model that the entire industry is based on. In

It is a myth that we can get systems "right the first time." Instead, we should implement only today's stories, then refactor and expand the system to implement new stories tomorrow. This is the essence of iterative and incremental agility. Test-driven development, refactoring, and the clean code they produce make this work at the code level.

The perfect kind of architecture decision is the one which never has to be made

The Dependency Inversion Principle (DIP) tells us that the most flexible systems are those in which source code dependencies refer only to abstractions, not to concretions.

It is a myth that we can get systems "right the first time." Instead, we should implement only today's stories, then refactor and expand the system to implement new stories tomorrow. This is the essence of iterative and incremental agility.