Quotes About Optimization

Figura 5.11. La pauta heijunka como estado objetivo. Heijunka es una de las técnicas más importante del arsenal de herramientas de Toyota, y un estado target u objetivo especialmente útil porque el esfuerzo por alcanzarlo arroja luz sobre muchos elementos del proceso de montaje y el flujo de valor asociado. Una vez que hayamos entendido que heijunka, o nivelación, no es un corsé, sino un estado objetivo, podremos cosechar mejor los beneficios de haber ido tras el mismo.

I love efficiencies and I love solving big problems, and I love working with people who create efficiencies. I love creating efficiencies in my own life on a day-to-day basis.

But I'd rather work smart than hard.

Debugging tip: For server applications, be sure to always specify the -server JVM command line switch when invoking the JVM, even for development and testing. The server JVM performs more optimization than the client JVM, such as hoisting variables out of a loop that are not modified in the loop; code that might appear to work in the development environment (client JVM) can break in the deployment environment (server JVM).

When used properly, threads can reduce development and maintenance costs and improve the performance of complex applications.

One of the very worst uses of time is to do something very well that need not to be done at all.

The law of increasing returns says that the more you focus on doing the few things that represent the most valuable use of your time, the better you become at those activities and the less time it takes you to accomplish each one.

One of the very worst uses of time is to do something very well that need not be done at all.

3. Apply the 80/ 20 Rule to everything: Twenty percent of your activities will account for 80 percent of your results. Always concentrate your efforts on that top 20 percent.

Dicho con sencillez, a algunas personas las cosas les van mejor porque hacen las cosas de un modo diferente y hacen correctamente las cosas adecuadas. Sobre todo, utilizan su tiempo mucho mejor que la persona promedio.

The Law of Forced Efficiency says, "There is never enough time to do everything, but there is always enough time to do the most important thing." Put another way, you cannot eat every tadpole and frog in the pond, but you can eat the biggest and ugliest one, and that will be enough, at least for the time being.

Identify the 20 percent of your products and services that account for 80 percent of your sales and profits. How could you sell more of them?

get the right people on the bus, get the wrong people off the bus, and then get the right people in the right seats on the bus.

No gastes neuronas en lo que no funciona.

This isn't about perfection. Far from it. It's simply about getting better — better in systematic and concrete ways that improve the company's bottom line.

Freed capacity is the result of process time reduction through the elimination of wasteful activities and/or optimizing work.

designing the ability to operate with fewer customer complaints, less firefighting, and reduced interdepartmental tension brings tremendous hope to leaders and their staffs who may be feeling the pressure from an underperforming value stream.

The inclination to jump into the weeds and design micro-level improvements before the entire work system - the macro picture- is fully understood, is a key contributor to suboptimization.

Compact code was inherently good since it consumed less internal memory. Consisting of slivers of silicon chips called DRAM ("dynamic-random-access-memories"), internal memory was like a gas tank. The larger the tank, the farther the car would go. The smaller the operating program, the more gas was left for all other programs. Because

Most code writers were like gifted athletes; they learned by doing and could not explain their actions. They just did it. This method, while fine for getting started, often hampered efforts at making code faster, which required unblinking self-analysis. "The secret to optimizing speed" he said, "is to ask yourself, 'What does this code actually need to do? What's the least work I can do to solve this problem?' " All

In most projects, the first system built is barely usable. It may be too slow, too big, awkward to use, or all three." Cutler

Pareto points us in a very clear direction: the majority of what you want will come from the minority of what you do.

Innumerable conditions must be exquisitely optimized for the support of humanity and of civilization. Many of them are highly time variable. Evidence showing that a wide variety of independent conditions all reached optimality during the identical narrow epoch when human beings appeared on the cosmic and terrestrial scene testifies of supernatural design and purpose rather than mere coincidence.

A travelling salesman has a hundred cities on his patch. He knows all the distances between every pair of cities. He needs to visit each city once and end up at his starting point. What's his shortest route?